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

Assignment type compatibiity test does not take synonyms into account #299

Closed
meijeru opened this Issue Nov 8, 2012 · 3 comments

Comments

Projects
None yet
2 participants
@meijeru

meijeru commented Nov 8, 2012

f: func [arg [integer!] /local i [int32!]][i: arg]

-= Red/System Compiler =-
Compiling tests/mytest.reds ...
*** Compilation Error: attempt to change type of variable: i
*** from: [int32!]
***   to: [integer!]
*** in file: %tests/mytest.reds
*** in function: f
*** at line: 2
*** near: [i: arg]

The curious thing is, that integer! and any enumeration type name are found to be compatible.

@dockimbel

This comment has been minimized.

Member

dockimbel commented Nov 8, 2012

int32! and uint8! are not part of the official Red/System specification anymore, see #283.

@meijeru

This comment has been minimized.

meijeru commented Nov 8, 2012

OK, I stand corrected, but it is still allowed to write int32! in places where a type is allowed. Shouldn't that be disallowed also?

@dockimbel

This comment has been minimized.

Member

dockimbel commented Nov 8, 2012

int32! and uint8! removed, int16! is still allowed in function spec as I need it for (unreleased) AVR8 backend.

dockimbel added a commit that referenced this issue Nov 8, 2012

@dockimbel dockimbel closed this Nov 8, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment