-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Rollup of 7 pull requests #93778
Rollup of 7 pull requests #93778
Conversation
…ce types or consts in GAT substs
…ator, r=matthewjasper Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
Do not suggest char literal for zero-length strings PR rust-lang#92507 adds a hint to switch to single quotes when a char is expected and a single-character string literal is provided. The check to ensure the string literal is one character long missed the 0-char case, and would incorrectly offer the hint. This PR adds the missing check, and a test case to confirm the new behavior.
Don't constrain projection predicates with inference vars in GAT substs cc rust-lang#91762 Not a fix, but a mitigation to prevent a backwards-compatible hazard where we normalize using a predicate only because it's the only one available, but shouldn't. This would constrain an inference variable which didn't really want. We already do this when selecting a projection candidate, which isn't always correct. But changing that is a problem for a different day. Also found out that a suggestion for `await`ing a future was using the wrong substs. r? ``@nikomatsakis``
Use `NtCreateFile` instead of `NtOpenFile` to open a file Generally the internal `Nt*` functions should be avoided but when we do need to use one we should stick to the most commonly used for the job. To that end, this PR replaces `NtOpenFile` with `NtCreateFile`. NOTE: The initial version of this comment hypothesised that this may help with some recent false positives from malware scanners. This hypothesis proved wrong. Sorry for the distraction.
add fut/back compat tests for implied trait bounds the `guard` test was tested to cause a segfault with `-Zchalk`, very nice cc ``@nikomatsakis`` rust-lang#44491 rust-lang#25860
…=lnicola ⬆️ rust-analyzer r? ``@ghost``
deduplicate `lcnr` in mailmap
@bors r+ rollup=never p=7 |
📌 Commit ff3324c has been approved by |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors retry rustdoc test timeout
|
⌛ Testing commit ff3324c with merge 70390e345bd0aedae2b617a9c79750ab052f63a2... |
@matthiaskrgr This is the error I was mentioning in Zulip. I opened #93784 to track the sporadic failures. |
💥 Test timed out |
@bors retry timeout of msvc-1, dist-x86_64-musl, x86_64-netbsd |
⌛ Testing commit ff3324c with merge a946ba5f49d1475def337d07a9b159c052258c0f... |
💔 Test failed - checks-actions |
The job Click to see the possible cause of the failure (guessed by this bot)
|
☀️ Test successful - checks-actions |
Finished benchmarking commit (9a5a961): 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 |
Successful merges:
static
#[global_allocator]
doesn'timpl
GlobalAlloc
#91950 (Point at type when astatic
#[global_allocator]
doesn'timpl
GlobalAlloc
)NtCreateFile
instead ofNtOpenFile
to open a file #93206 (UseNtCreateFile
instead ofNtOpenFile
to open a file)lcnr
in mailmap #93767 (deduplicatelcnr
in mailmap)Failed merges:
r? @ghost
@rustbot modify labels: rollup
Create a similar rollup