-
-
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
Function redefinition doesn't always work #17076
Comments
I was wondering when someone would notice this. (not a duplicate of #265) |
You want to explain what you changed, @vtjnash? |
I had been finding this also, kinda thought either it was by design (no redefining consts) or that someone else had reported it. |
Apparently not? |
What better way to explain? |
A function with no comments or tests doesn't actually explain what was going wrong in a way that anyone other than you understands. |
I found that sometimes function overwriting does not work right away. The method redefinition warning gets triggered, but the old function definition is used.
Here is a minimal test case which shows the bug (the last call fails, but calling
f()
again then produces2
as expected):This is on version
0.5.0-dev+4882
.The text was updated successfully, but these errors were encountered: