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
{{ message }}
Repository navigation
injected code results in errors that emacs hates #3530
<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.
intrinsic.rs is moving to core now that we have #[lang] items; core-macros will also go away when we figure out a mechanism for pulling in syntax extensions and/or macro definitions in other crates.
In general I think "pointing to source files on disk" isn't going to work so well, since it implies the end-user has a source-file. I'd prefer not to be shipping .rs files as part of the end-user distribution / make install file set.
these macro errors produce a "note: expansion site" message, right? perhaps the emacs plugin could be configured to recognise a string such as "" and look for the expansion site message below.
Activity
graydon commentedon Sep 19, 2012
intrinsic.rsis moving to core now that we have#[lang]items;core-macroswill also go away when we figure out a mechanism for pulling in syntax extensions and/or macro definitions in other crates.In general I think "pointing to source files on disk" isn't going to work so well, since it implies the end-user has a source-file. I'd prefer not to be shipping .rs files as part of the end-user distribution /
make installfile set.catamorphism commentedon Dec 28, 2012
Bumping to 0.7; this seems like low priority compared to the million and one traits bugs.
catamorphism commentedon Apr 25, 2013
Not critical for 0.7. Nominating for milestone 5, production-ready.
graydon commentedon May 9, 2013
should say something that does not make emacs mad, but there is no file to point to.
graydon commentedon May 9, 2013
accepted for production-ready milestone
emberian commentedon Jul 7, 2013
still relevant
bblum commentedon Aug 19, 2013
these macro errors produce a "note: expansion site" message, right? perhaps the emacs plugin could be configured to recognise a string such as "" and look for the expansion site message below.
pnkfelix commentedon Aug 27, 2013
part of #8793
pnkfelix commentedon Jan 22, 2014
assigning P-low.
steveklabnik commentedon Jan 21, 2015
Triage: I don't use emacs, but these errors are the same, so I'm guessing this is still the same.
steveklabnik commentedon Feb 2, 2015
Moved to rust-lang/rust-mode#4
submodules: update clippy from b7a431e to a416c5e
Auto merge of #56853 - matthiaskrgr:clippy, r=oli-obk
Merge pull request rust-lang#3530 from xiongmao86/issue2941
Auto merge of rust-lang#3531 - narpfel:quiet-sysroot, r=RalfJung
Merge rust-lang#3530