-
-
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
Rebase no load error on macroexpand #38379
Conversation
Credit for the deprecation code goes to @c42f |
XRef: this is a continuation of: #37857 Note that, generally speaking, it's better to force push your WIP branch when doing a rebase, rather than opening a new PR. This makes it easier for reviewers.
Thanks. By the way, the "git standard" way to add multiple authors is to add a |
Oh, ok! Is it possible to edit the existing commit to include |
Pretty sure the failure here is unrelated (maybe there's profile deadlocking on Arch?) |
Sure - use |
Co-authored-by: Chris Foster <[email protected]>
6da368d
to
b2233b0
Compare
Thanks for the help! Hopefully that did it |
Bump? |
Could use a news entry. |
Ok! How's that look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking close, I added a couple more suggestions for backward compat.
stdlib/Test/test/runtests.jl
Outdated
throw(ErrorException("Real error")) | ||
end | ||
macro test_macro_throw_2() | ||
LoadError("file", 111, throw(ErrorException("Real error"))) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks weird — it throws ErrorException
so that LoadError
is doing nothing. I see it's carried over from 3ee9d8f, but it was probably a mistake there too.
IIRC the intention here was to actually throw LoadError
explicitly, as the occasional non-core library does that to mimic Base.
Ok, I've added a deprecation warning to undecorated |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, we're very close here. depwarn()
is subtle to use correctly.
There's some test errors here to investigate. I'm not sure whether we still run all tests with --depwarn=error
by default, but that might be the cause. In that case, these deprecation tests might need to be treated the same as test/deprecation_exec.jl
(see test/misc.jl
for how that is run)
Co-authored-by: Chris Foster <[email protected]>
Look at all that green! |
Bump. @JeffBezanson? |
Wooo!!! |
adapt to JuliaLang/julia#38379 Co-authored-by: Lyndon White <[email protected]>
used for all settings-related errors fix use of LoadError in tests (JuliaLang/julia#38379) also simplify the `defaults` macro in src/common.jl
No description provided.