Skip to content
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

injected code results in errors that emacs hates #4

Closed
steveklabnik opened this issue Feb 2, 2015 · 1 comment
Closed

injected code results in errors that emacs hates #4

steveklabnik opened this issue Feb 2, 2015 · 1 comment

Comments

@steveklabnik
Copy link
Member

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:

<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.

@MicahChalmer
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants