Expose default namespace object. #24
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is useful for when you still only have a single global namespace and want to use the global `signal` helper function, but want to be able to modify or inspect that namespace. This also makes it possible to write consistent code that is parameterized on a namespace, but can still function with the global namespace. This also enables support for diagnostic tools that inspect the global namespace.
|
This is too old to merge cleanly, but the idea makes sense, so I've done it in the current code in #145. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This also supports diagnostic utilities that inspect the global namespace. This also makes it convenient to write consistent code that is parameterized on a namespace, but that still functions with the global namespace. Additionally, not exposing the global namespace encourages writing codes that refers to it only implicitly, which is more painful to refactor later.
In those use cases, the alternative to library users is something brittle like:
For additional discussion, see the original PR #23