We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I got this error (I missed a ?):
?
error[E0369]: binary operation `!=` cannot be applied to type `std::result::Result<flow::EventContour, flow::Error>` --> crates/front/cli/src/lib.rs:245:23 | 245 | while found.run(ParkState::None, &self.tx, CLIComms) != flow::EventContour::Finishing {} | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | note: an implementation of `std::cmp::PartialEq` might be missing for `std::result::Result<flow::EventContour, flow::Error>` --> crates/front/cli/src/lib.rs:245:23 | 245 | while found.run(ParkState::None, &self.tx, CLIComms) != flow::EventContour::Finishing {} | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
There's no information gained by printing the span again. Maybe there is some situation where it isn't the same?
The text was updated successfully, but these errors were encountered:
It seems to be always the same span (namely lhs_expr.span).
lhs_expr.span
Sorry, something went wrong.
Rollup merge of rust-lang#39707 - durka:parsimonious-span-note, r=jon…
84ad515
…athandturner change span_notes to notes in E0368/E0369 Fixes rust-lang#39650. All the uses of `span_note` in these errors were reusing the same span as the original error, which causes unnecessary repetition. For an example, see the changes to [src/test/ui/span/issue-39018.stderr](https://github.com/rust-lang/rust/pull/39707/files?diff=unified#diff-46336f62958fdb34233db414cb9914a1R4). r? @jonathandturner
No branches or pull requests
I got this error (I missed a
?
):There's no information gained by printing the span again. Maybe there is some situation where it isn't the same?
The text was updated successfully, but these errors were encountered: