-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
minor: Sync from rust #14767
minor: Sync from rust #14767
Conversation
@@ -39,7 +39,7 @@ fn benchmark_parser() { | |||
let _b = bench("parsing"); | |||
let p = SourceFile::parse(&data); | |||
assert!(p.errors.is_empty()); | |||
assert_eq!(p.tree().syntax.text_range().len(), 352474.into()); | |||
assert_eq!(p.tree().syntax.text_range().len(), 352458.into()); |
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.
Because of the fmt
changes, maybe?
This reverts commit abc0660118cc95f47445fd33502a11dd448f5968.
This function/lang_item was introduced in #104321 as a temporary workaround of future lowering. The usage and need for it went away in #104833. After a bootstrap update, the function itself can be removed from `std`.
Dropped the two commits from rust-lang/rust#109002 because they break building against the stable sysroot. |
Actually, according to #13676 (comment), it seems we can't drop commits that way. |
Hmm, can we add those commits and merge them in without CI approval? Then fix them up afterwards? |
Ahh nevermind I see the issue now |
Yes, but we'll have to propagate our "fix" downstream, if it involves changing the code there 😄 . |
No description provided.