-
Notifications
You must be signed in to change notification settings - Fork 13.4k
"typed" pretty printing mode fails with "unresolved name" for macros with variables #691
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
Comments
pdietl
pushed a commit
to pdietl/rust
that referenced
this issue
Apr 23, 2020
Add macros in extern blocks and new proc-macro support.
bors
pushed a commit
to rust-lang-ci/rust
that referenced
this issue
Oct 26, 2020
Eg when the local is immutable **and** the type is freeze. This makes the simple raytracer runtime benchmark 1% faster than cg_llvm without optimizations. Before it was 2% slower. cc rust-lang#691 cc rust-lang#684
bjorn3
added a commit
to bjorn3/rust
that referenced
this issue
Aug 6, 2021
In case of PassMode::Indirect, the ownership of the backing storage is transfered to the callee. This means that the caller must copy the argument if it wants to use it again later. Fixes rust-lang#691
tgross35
added a commit
to tgross35/rust
that referenced
this issue
Jun 3, 2025
…5T14-37-02Z chore: release v0.1.128
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For example, in
It will produce "unresolved name" errors for x, body, and y.
I'm not really sure if there is a good way to fix this. Typechecking depends on macro expansion but pretty printing after macro expansion is quite different from pretty printing before it...
The text was updated successfully, but these errors were encountered: