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

Improving Use of Scoping #405

Open
DavePearce opened this issue Nov 29, 2024 · 0 comments
Open

Improving Use of Scoping #405

DavePearce opened this issue Nov 29, 2024 · 0 comments

Comments

@DavePearce
Copy link
Collaborator

DavePearce commented Nov 29, 2024

Currently, the way that buildModuleScope() works is not ideal at all. Realistically, we need to remove the Environment entirely from the resolution process, and only generate the schema after resolution. The problem is that, at the moment, the ModuleScope is only constructed after assignments have been resolved. However, in the future when we have defcompute constructs then this will not work as we may need to resolve expressions at the same time?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant