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

Minor issues in docs regarding keywords #9725

Closed
awr1 opened this issue Nov 15, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@awr1
Copy link
Contributor

commented Nov 15, 2018

  • Relevant section: unsafeAddr is not listed as a keyword, I think it should be added as it functions similar to addr but has special semantics with let.
  • Relevant section: The section on identifier partial case insensitivity should be expanded to mention that the same follows for keywords.
@Araq

This comment has been minimized.

Copy link
Member

commented Nov 15, 2018

  • unsafeAddr is not a keyword, the spec shouldn't lie.
  • Ok.
@krux02

This comment has been minimized.

Copy link
Contributor

commented Nov 16, 2018

I would like to add, that we plan to emit warnings, when a keyword isn't the standard way of using a keyword. For example vA_r is identical to var but it is certainly counterproductive to ever use it.

@awr1

This comment has been minimized.

Copy link
Contributor Author

commented Nov 16, 2018

Is the "canonical" way to type out identifiers just all lowercase? No notIn or isNot, rather notin and isnot?

@Araq

This comment has been minimized.

Copy link
Member

commented Nov 17, 2018

Yes, notin and isnot.

narimiran added a commit to narimiran/Nim that referenced this issue Jan 30, 2019

@narimiran narimiran closed this in 3d6f2b7 Jan 30, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.