Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SIMPLE-VECTOR #435

Open
kasper-pixelated-noise opened this issue Mar 29, 2022 · 5 comments
Open

SIMPLE-VECTOR #435

kasper-pixelated-noise opened this issue Mar 29, 2022 · 5 comments

Comments

@kasper-pixelated-noise
Copy link

ABCL:

CL-USER(1): (typep #(1 2) '(simple-vector 2))
T

JSCL

CL-USER>  (typep #(1 2) '(simple-vector 2))
ERROR: Unknown type-specifier (SIMPLE-VECTOR 2).
@davazp
Copy link
Member

davazp commented Sep 2, 2022

Is it done? I'm still getting the same error.

@vlad-km
Copy link
Member

vlad-km commented Sep 2, 2022

At now In JSCL any one-dimensional array - its a simple vector.
I dont think that before the implementation of the subtypep, its necessary to multiply entities.
In case of emergency - we has a deftype - any type at any time.

@davazp
Copy link
Member

davazp commented Sep 2, 2022

Sure but then (typep #(1 2) '(simple-vector 2)) should return T instead of throwing the error?

@vlad-km
Copy link
Member

vlad-km commented Sep 2, 2022

Hmmm
I'll take care

@vlad-km vlad-km reopened this Sep 2, 2022
@vlad-km
Copy link
Member

vlad-km commented Sep 8, 2022

@davazp

Well
To start

  1. I did not define such a type either in hardcode or as user-defined via DEFTYPE

  2. I would like to look at the type definition through the DEFTYPE of this type in order to first determine the scale of the problem and how to solve it

  3. In the general case, this problem is solved by a competent definition (DEFTYPE simple-vector...) on the user side

  4. For most users, there is no difference between vector and simple-vector other than the simple- name prefix. For a user who has this difference, there is a DEFTYPE (this is a custom case, completely on his side, with all the side effects of the current implementation).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants