diff options
| author | bors <bors@rust-lang.org> | 2023-03-01 09:13:23 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-03-01 09:13:23 +0000 |
| commit | 64165aac68af780182ff89a6eb3982e3c262266e (patch) | |
| tree | 3d1c85df18f1b4598b9ad855146bfc312cd1752e /tests/rustdoc-js-std/parser-errors.js | |
| parent | bcb610da7fae8297689883782601ecb8645604e2 (diff) | |
| parent | 5448123a11c88a6e62d5f804a965a88e773a61cd (diff) | |
| download | rust-64165aac68af780182ff89a6eb3982e3c262266e.tar.gz | |
Auto merge of #108476 - saethlin:remove-library-rustc-box, r=thomcc
Remove or document uses of #[rustc_box] in library
r? `@thomcc`
Only one of these uses is tested for in the rustc-perf benchmark suite. The impact there on compile time is somewhat dramatic, but I am inclined to make this change as a simplification to the library and wait for people to complain if it explodes their compilation time. I think in the absence of data or reports from users about what code paths really matter, if we are optimizing for compilation time, it's hard to argue against using `#[rustc_box]` everywhere we currently call `Box::new`.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions