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

Shade everything in a subpackage #35

Open
propensive opened this issue Jan 20, 2023 · 1 comment
Open

Shade everything in a subpackage #35

propensive opened this issue Jan 20, 2023 · 1 comment
Assignees
Labels
code quality Concerns the standard of code rather than functionality enhancement An improvement to existing functionality

Comments

@propensive
Copy link
Owner

When building a release version of Fury, it should be possible to write package fury at the start of every source file and everything will be put into a fury-prefixed subpackage which will be visible everywhere inside Fury's source, which is all in the fury package. These packages will then be invisible (except when importing fury) from inside the Scala compiler running inside Fury.

Some care must be taken not to use the _root_ prefix anywhere, though.

@propensive propensive self-assigned this Jan 20, 2023
@propensive propensive added enhancement An improvement to existing functionality code quality Concerns the standard of code rather than functionality labels Oct 8, 2023
@github-project-automation github-project-automation bot moved this to Todo in Soundness Oct 8, 2023
@propensive propensive moved this from Todo to Started in Soundness Oct 8, 2023
@propensive
Copy link
Owner Author

This is becoming increasingly important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code quality Concerns the standard of code rather than functionality enhancement An improvement to existing functionality
Projects
Status: Started
Development

No branches or pull requests

1 participant