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

feat: support perspective name qualification #501

Closed
DavePearce opened this issue Jan 7, 2025 · 1 comment · Fixed by #504
Closed

feat: support perspective name qualification #501

DavePearce opened this issue Jan 7, 2025 · 1 comment · Fixed by #504
Assignees

Comments

@DavePearce
Copy link
Collaborator

The exp benchmark uses perspectives, and also makes use of "perspective qualified names" of the form perspective/column. These need to be supported so this test can be enabled.

@DavePearce
Copy link
Collaborator Author

I think the pathway here is:

  • Adjust Symbol so that it now has a Path.
  • A Path can be relative or absolute (the latter being rooted in a particular module).
  • Allow modules to be nested.
  • Manage issue of looking up relative names (e.g. Path.Child() for example).
  • Can we then remove the GlobalScope entirely I wonder?

@DavePearce DavePearce linked a pull request Jan 8, 2025 that will close this issue
@DavePearce DavePearce self-assigned this Jan 8, 2025
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

Successfully merging a pull request may close this issue.

1 participant