Repository navigation
Conversation
|
Let's see which debuggers break this time |
This comment has been minimized.
This comment has been minimized.
Nuke Unique try-job: test-aarch64-apple-1 try-job: test-x86_64-msvc-1
|
rust-analyzer has a lint for The command at the top to regenerate the file doesn't work, I filed an issue at rust-lang/rust-analyzer#23501. If CI works without changing the file, then I'm in favor of just ignoring it, since idk if the lint would actually get auto-removed from us deleting the relevant parts of std, or if it's generated independently. |
|
r? hanna-kruppe |
There was a problem hiding this comment.
Good riddance!
I almost want to wait a little longer because I'm fully expecting someone to show up with a regression that forces us to revert the previous PRs that made this possible. But I guess if we have to revert those, reverting this as well will be trivial. So let's go ahead and flush out the remaining uses of Unique in the ecosystem :)
@bors r+ rollup
There was a problem hiding this comment.
This looks like a genuine regression test that just happened to use Unique and which we might want to keep. But it turns out the issue = "0" thing has been removed long ago (see #41260 and the PRs referencing it), so we don’t need this test any more.
|
@bors rollup |
|
btw there are some lingering references in debug visualizers: The latter two |
|
Hmm, right, I only searched for |
|
Does the removed feature need to be documented? We did make the it's a very internal feature, I'm not sure whether it matters... |
|
Do we document every ad-hoc internal feature that is later removed? Ofc, |
No description provided.