-
Notifications
You must be signed in to change notification settings - Fork 13.3k
suggest removing type ascription in bad parsing position #95104
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
Conversation
r? @davidtwco (rust-highfive has picked a reviewer for you, use r? to override) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I had a dig through the existing tests but nothing obvious jumped out at me as a flag/option for testing this as-if it was a stable compiler, should be fine without for this case though.
@bors r+ rollup |
📌 Commit 3516a16 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (051d117): comparison url. Summary: This benchmark run did not return any relevant results. 3 results were found to be statistically significant but too small to be relevant. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Not sure how to test this with the non-nightly suggestion. Didn't add a new UI test because it already manifests in an existing UI test.
Fixes #95014