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

Enforce legality of variable names at (define) #914

Closed
kantai opened this issue Feb 6, 2019 · 2 comments
Closed

Enforce legality of variable names at (define) #914

kantai opened this issue Feb 6, 2019 · 2 comments
Assignees
Labels
bug Unwanted or unintended property causing functional harm locked

Comments

@kantai
Copy link
Member

kantai commented Feb 6, 2019

Right now, almost all variables are fair game in (define) and (let), though the lookup path for reserved names prevents overriding +, etc.

A related issue is that in the interpreter, variables and functions are logically in two different namespaces (this helps with typing at the interpreter level, because functions are not value types). Of course, we want to prevent overlapping defines of variables/functions as well.

@kantai kantai self-assigned this Feb 6, 2019
@kantai kantai added the bug Unwanted or unintended property causing functional harm label Feb 6, 2019
@kantai
Copy link
Member Author

kantai commented Feb 26, 2019

This was merged into #921

@kantai kantai closed this as completed Feb 26, 2019
@blockstack-devops
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Dec 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Unwanted or unintended property causing functional harm locked
Projects
None yet
Development

No branches or pull requests

2 participants