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

The primitive type names and the literal suffixes are not matched #56

Closed
lumynou5 opened this issue May 20, 2022 · 2 comments
Closed

The primitive type names and the literal suffixes are not matched #56

lumynou5 opened this issue May 20, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers language spec about casc's lang spec ;)

Comments

@lumynou5
Copy link

The primitive type names and the literal suffixes are not matched; for example, the type is i32 but the literal is 1I.

@ChAoSUnItY
Copy link
Member

Ok, so it went out in CASC number naming covention is not that easily to describe. For all integers, inlcuding byte, short, int, and long, they are all sharing a integer prefix which is i in this case. So for i32, it shouldn't be 1I, instead, it should be 1i32.

And so on, to specify a number literal's type, you should add corresponding type name after it.

@ChAoSUnItY ChAoSUnItY self-assigned this May 20, 2022
@ChAoSUnItY ChAoSUnItY added enhancement New feature or request good first issue Good for newcomers language spec about casc's lang spec ;) labels May 20, 2022
@ChAoSUnItY ChAoSUnItY mentioned this issue Jun 10, 2022
5 tasks
@ChAoSUnItY
Copy link
Member

afaik, this issue had been fixed, as example showed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers language spec about casc's lang spec ;)
Projects
None yet
Development

No branches or pull requests

2 participants