-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
behavior of attempting to redefine constants #258
Comments
JeffBezanson
added a commit
that referenced
this issue
Nov 14, 2011
StefanKarpinski
added a commit
that referenced
this issue
Nov 15, 2011
* 'master' of github.com:JuliaLang/julia: use uninitialized arrays in find(). fix array type in nonzeros(). warning instead of error for const redefinition. fixes issue #258.
KristofferC
added a commit
that referenced
this issue
Apr 26, 2018
Keno
pushed a commit
that referenced
this issue
Apr 27, 2018
LilithHafner
pushed a commit
to LilithHafner/julia
that referenced
this issue
Oct 11, 2021
Add ambiguity detection to the package tests and temporarily mark the test as broken
cmcaine
pushed a commit
to cmcaine/julia
that referenced
this issue
Nov 11, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Often a source file might define some constants, and you want to reload it to change some function definitions, but the constants don't change. Maybe instead of an error, we should print a warning that the redefinitions were ignored. Same goes for type declarations.
Another way to approach this is to change loading behavior so that every expression in a file is evaluated even if some cause errors. Instead of stopping we show the exception and move on.
The text was updated successfully, but these errors were encountered: