-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Open
Labels
A-MIRArea: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.htmlArea: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.htmlA-closuresArea: Closures (`|…| { … }`)Area: Closures (`|…| { … }`)A-prettyArea: Pretty printing (including `-Z unpretty`)Area: Pretty printing (including `-Z unpretty`)C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
Description
Quoting @eddyb in #66850 (comment)
I'm not that happy with
[closure@PATH::{{closure}}#n ...]
, but it's consistent with what we have so far, if we want to go further I'd prefer something like this:foo<T>::{closure#0} { q:&i32, t:&T }(yes,
{{closure}}#n
->{closure#n}
is a change we should do eventually, IMO)
and without-Z span_free_formats
we could perhaps go for:closure(src/main.rs:10:13) { q:&i32, t:&T }(and we need to remember to fix generators as well)
Oh and we could also change
fn
definition types from:fn(bool) -> bool {std::convert::identity::<bool>}to:
fn std::convert::identity::<bool>(bool) -> bool
Metadata
Metadata
Assignees
Labels
A-MIRArea: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.htmlArea: Mid-level IR (MIR) - https://blog.rust-lang.org/2016/04/19/MIR.htmlA-closuresArea: Closures (`|…| { … }`)Area: Closures (`|…| { … }`)A-prettyArea: Pretty printing (including `-Z unpretty`)Area: Pretty printing (including `-Z unpretty`)C-enhancementCategory: An issue proposing an enhancement or a PR with one.Category: An issue proposing an enhancement or a PR with one.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.