-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Do not point at whole file missing fn main
#93142
Conversation
r? @wesleywiser (rust-highfive has picked a reviewer for you, use r? to override) |
This comment has been minimized.
This comment has been minimized.
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.
Looks like one UI test still needs to be blessed. r=me after that!
6cccce1
to
d6c508b
Compare
@bors r=wesleywiser |
📌 Commit d6c508b has been approved by |
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
looks like a test failed :( |
☔ The latest upstream changes (presumably #92007) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r+ |
📌 Commit c7ff23f has been approved by |
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
Do not point at whole file missing `fn main` Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
Looks like tests need to be reblessed #94532 (comment) |
@bors r=wesleywiser rollup=never |
📌 Commit 12df043e4cedebf9ba03210ec6d6ec9189f6d12e has been approved by |
⌛ Testing commit 12df043e4cedebf9ba03210ec6d6ec9189f6d12e with merge d3650bc60fb43f72684c1a3ed90fc521abd71dcf... |
💔 Test failed - checks-actions |
This comment has been minimized.
This comment has been minimized.
Only point at the end of the crate. We could try making it point at the beginning of the crate, but that is confused with `DUMMY_SP`, causing the output to be *worse*. This change will make it so that VSCode will *not* underline the whole file when `main` is missing, so other errors will be visible.
🤦♂️ forgot about clippy tests @bors r=wesleywiser |
📌 Commit 91f3603 has been approved by |
☀️ Test successful - checks-actions |
Finished benchmarking commit (8c93948): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Only point at the end of the crate. We could try making it point at the
beginning of the crate, but that is confused with
DUMMY_SP
, causingthe output to be worse.
This change will make it so that VSCode will not underline the whole
file when
main
is missing, so other errors will be visible.