diff options
| author | bors <bors@rust-lang.org> | 2022-07-20 22:19:30 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-07-20 22:19:30 +0000 |
| commit | be9cfb307e6928600a9769695e02d6296e8e1174 (patch) | |
| tree | b1903315be648e06cd6a24880801ef5e0ac22024 /compiler/rustc_llvm/llvm-wrapper/Linker.cpp | |
| parent | d68e7ebc38cb42b8b237392b28045edeec761503 (diff) | |
| parent | 88f6c6d8a0245938f9f49e8b088114d6862e793d (diff) | |
| download | rust-be9cfb307e6928600a9769695e02d6296e8e1174.tar.gz rust-be9cfb307e6928600a9769695e02d6296e8e1174.zip | |
Auto merge of #99058 - michaelwoerister:remove-stable-set-and-map, r=nagisa
Remove the unused StableSet and StableMap types from rustc_data_structures. The current implementation is not "stable" in the same sense that `HashStable` and `StableHasher` are stable, i.e. across compilation sessions. So, in my opinion, it's better to remove those types (which are basically unused anyway) than to give the wrong impression that these are safe for incr. comp. I plan to provide new "stable" collection types soon that can be used to replace `FxHashMap` and `FxHashSet` in query results (see [draft](https://github.com/michaelwoerister/rust/commit/69d03ac7a7d651a397ab793e9d78f8fce3edf7a6)). It's unsound that `HashMap` and `HashSet` implement `HashStable` (see https://github.com/rust-lang/rust/issues/98890 for a recent P-critical bug caused by this) -- so we should make some progress there.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/Linker.cpp')
0 files changed, 0 insertions, 0 deletions