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

Don't export polyglot symbols #3915

Merged
merged 4 commits into from
Nov 28, 2022

Conversation

hubertp
Copy link
Contributor

@hubertp hubertp commented Nov 25, 2022

Pull Request Description

By default all polyglot symbols that have been imported were always exported. This means that importing a module that had some polyglot imports brought them into the scope automatically. This didn't follow our desired semantics.

Fixes task 3 in https://www.pivotaltracker.com/story/show/183833055.

Checklist

Please include the following checklist in your PR:

  • The documentation has been updated if necessary.
  • All code conforms to the
    Scala,
    Java,
    and
    Rust
    style guides.
  • All code has been tested:
    • Unit tests have been written where possible.
    • If GUI codebase was changed: Enso GUI was tested when built using BOTH
      ./run ide build and ./run ide watch.

@hubertp hubertp changed the title Don't export polyglot imports Don't export polyglot symbols Nov 25, 2022
By default all polyglot symbols that have been imported were always
exported. This means that importing a module that had some polyglot
imports brought them into the scope automatically.
This didn't follow our desired semantics.
@hubertp hubertp force-pushed the wip/hubert/dont-export-polyglotsymbols-183833055 branch from b5847ca to e40d875 Compare November 28, 2022 11:03
@hubertp hubertp added the CI: Ready to merge This PR is eligible for automatic merge label Nov 28, 2022
@mergify mergify bot merged commit c87d1d6 into develop Nov 28, 2022
@mergify mergify bot deleted the wip/hubert/dont-export-polyglotsymbols-183833055 branch November 28, 2022 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI: Ready to merge This PR is eligible for automatic merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants