-
Notifications
You must be signed in to change notification settings - Fork 13.3k
No line number in error message with try! macro #33704
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
Labels
A-macros
Area: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
Comments
cc @nrc |
ah I think I saw this bug when @jonathandturner and I were considering how best to render those stack traces... I feel like there was a simple logic bug in the "expand-macro-backtrace" code that led to it... @jonathandturner do you remember? |
I tried to track this regression via bisection and I arrived at 01d2b4a as the culprit |
note that #33730 has a fix |
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
May 19, 2016
…ostics, r=nikomatsakis Fix macro expansion backtrace diagnostics Fixes rust-lang#33704. r? @nikomatsakis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Playpen link: https://is.gd/eYoVIw
Using Stable or Beta, the error message looks like this:
The key part is that it tells me that line 6 is where the try expansion happens.
But when running with Nightly, this is the error message (in full):
The expansion site (line 6) is missing from the error diagnostics. While the playpen uses the new-style diagnostics, this problem (the missing line number) applies to the old-style diagnostics too.
I'm not sure if this is only for
try!
, or if it is for all macros (I didn't test that)I'm not sure exactly what version of rustc the playpen is at, but this issue is reproduced with
rustc 1.10.0-nightly (cd6a40017 2016-05-16)
The text was updated successfully, but these errors were encountered: