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.

Sign up for GitHub

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

Jump to bottom

Improve Naming of Evnrionment Slots #52

Open
iwillspeak opened this issue Nov 20, 2021 · 1 comment
Open

Improve Naming of Evnrionment Slots #52

iwillspeak opened this issue Nov 20, 2021 · 1 comment
Labels
feature New feature or request up for grabs Shout out and claim this issue

Comments

@iwillspeak
Copy link
Owner

Current environment slot naming is of the form _env_0 where 0 is the slot index. It would be nice if this better represented the value that is to be stored there e.g. if captured from an argument it could be _arg_0 or _local_1 for locals. Even better if the field name could include the original name for the field, although this may require some tweaks to how StorageRef is represented to flow that information through to the emit phase.
@iwillspeak iwillspeak added feature New feature or request up for grabs Shout out and claim this issue labels Nov 20, 2021
@iwillspeak
Copy link
Owner Author

See also the namimg discussions in #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature or request up for grabs Shout out and claim this issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@iwillspeak