Update compiler error 0027 to use new error format. #35410
Conversation
|
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @jonathandturner (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
|
@silenuss That's... the wrong issue linked, and you'll probably need to squash your commits. |
silenuss
force-pushed
the
e0027-formatting
branch
from
89f21c5 to
fa06c42
Compare
|
Ugh, my bad, thanks for the heads up. Anyways I just squashed the commits. |
silenuss
force-pushed
the
e0027-formatting
branch
from
fa06c42 to
c9e9d42
Compare
|
Thanks for the PR! @bors r+ rollup |
|
📌 Commit c9e9d42 has been approved by |
…andturner Update compiler error 0027 to use new error format. Part of rust-lang#35233, Addresses rust-lang#35200 r? @jonathandturner
…andturner Update compiler error 0027 to use new error format. Part of rust-lang#35233, Addresses rust-lang#35200 r? @jonathandturner
…andturner Update compiler error 0027 to use new error format. Part of rust-lang#35233, Addresses rust-lang#35200 r? @jonathandturner
…andturner Update compiler error 0027 to use new error format. Part of rust-lang#35233, Addresses rust-lang#35200 r? @jonathandturner
Part of #35233,
Addresses #35200
r? @jonathandturner