-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rustc nightly points out a wrong part of line as an error #90101
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Assigning priority as discussed in the Zulip thread of the Prioritization Working Group. @rustbot label -I-prioritize +P-medium |
I did a bisection and here is the result. bisected with cargo-bisect-rustc v0.6.1Host triple: x86_64-unknown-linux-gnu cargo bisect-rustc --prompt --test-dir=. --start=2021-08-01 --end=2021-10-20 |
I feel the span of the diagnostic before the regression is also erroneous.
Should ideally be something like below:
|
…r=estebank fix(rustc_typeck): report function argument errors on matching type Fixes rust-lang#90101
I tried this code (playground):
and rustc shows the following error:
Rustc says that
"world"
at line 6 is causing the error, but actually it is not.I think Rustc should point out
Path::new("hello").to_path_buf().to_string_lossy()
instead.Rustc version
# rustc --version --verbose rustc 1.58.0-nightly (1af55d19c 2021-10-19) binary: rustc commit-hash: 1af55d19c7a9189374d89472f97dc119659bb67e commit-date: 2021-10-19 host: x86_64-unknown-linux-gnu release: 1.58.0-nightly LLVM version: 13.0.0
The text was updated successfully, but these errors were encountered: