You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was labelled with: A-diagnostics, A-tools, I-wrong, P-low in the Rust repository
For example:
<core-macros>:3:10: 3:61 note: in expansion of #error
Emacs wants to load <core-macros> and interrupts your workflow to prompt for it. Injected code should come from files on disk (like intrinsic.rs) and we should use the correct file path when inserting them into the AST, so that the error messages work.
Alternately, we can come up with another way to indicate injected code so that the diagnostic emitter can generate error messages that emacs doesn't complain about. This could be a better solution, since getting dumped into core_macros.rs may not be so useful.
The text was updated successfully, but these errors were encountered:
I'm going to call this closed by #84. With that in place, it stops thinking that the lines <std macros> lines are errors, and doesn't prompt for a file name when you call next-error.
Issue by brson
Wednesday Sep 19, 2012 at 00:56 GMT
For earlier discussion, see rust-lang/rust#3530
This issue was labelled with: A-diagnostics, A-tools, I-wrong, P-low in the Rust repository
For example:
Emacs wants to load
<core-macros>
and interrupts your workflow to prompt for it. Injected code should come from files on disk (like intrinsic.rs) and we should use the correct file path when inserting them into the AST, so that the error messages work.Alternately, we can come up with another way to indicate injected code so that the diagnostic emitter can generate error messages that emacs doesn't complain about. This could be a better solution, since getting dumped into core_macros.rs may not be so useful.
The text was updated successfully, but these errors were encountered: