-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
err variable trashes global #48299
Comments
Has nothing to do with |
Correct - though it should get some documentation, which
|
vtjnash
added a commit
to vtjnash/julia
that referenced
this issue
Jan 16, 2023
This hides them from `names()` unfortunately, but means we will not accidentally discard a variable from the user in Main, either because the import will fail or the assignment will fail. If we later have world-versioned bindings, this would also mean you could toggle (between worlds) between being module-local and a special import value. Fix JuliaLang#43172 Fix JuliaLang#48299
vtjnash
added a commit
to vtjnash/julia
that referenced
this issue
Feb 14, 2023
This hides them from `names()` unfortunately, but means we will not accidentally discard a variable from the user in Main, either because the import will fail or the assignment will fail. If we later have world-versioned bindings, this would also mean you could toggle (between worlds) between being module-local and a special import value. This also needed some improvements to docs, so that it would print docstrings for unassigned globals without also simultaneously claiming that it did not exist. Fix JuliaLang#43172 Fix JuliaLang#48299
vtjnash
added a commit
that referenced
this issue
Feb 15, 2023
This hides them from `names()` unfortunately, but means we will not accidentally discard a variable from the user in Main, either because the import will fail or the assignment will fail. If we later have world-versioned bindings, this would also mean you could toggle (between worlds) between being module-local and a special import value. This also needed some improvements to docs, so that it would print docstrings for unassigned globals without also simultaneously claiming that it did not exist. Fix #43172 Fix #48299
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just discovered the @enum macro, which I love, but does some wrong error handling.
The text was updated successfully, but these errors were encountered: