diff options
| author | bors <bors@rust-lang.org> | 2024-10-06 11:24:28 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-10-06 11:24:28 +0000 |
| commit | 2d2e8cc21fe8327f9c4eb73b6d15e934d2f43370 (patch) | |
| tree | 4ebfc9930693c8bb1e2fa6a40799014a0bc4abf8 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 753629bb33c9fff9fb693a2d1d4464bd696ccf62 (diff) | |
| parent | 995eb95000f5c7010727f895d41f6d53fa6f242c (diff) | |
| download | rust-2d2e8cc21fe8327f9c4eb73b6d15e934d2f43370.tar.gz rust-2d2e8cc21fe8327f9c4eb73b6d15e934d2f43370.zip | |
Auto merge of #13485 - GnomedDev:reduce-large-threshold, r=xFrednet
Reduce default 'large array' threshold
As-is this threshold is `512kb`, but as #9449 points out this is way too high for most people to consider sensible (why would you want to copy `256kb` of data around on the stack or duplicate it via `const`) and didn't get any discussion when originally added. This PR reduces it the threshold to `1kb`, which is higher than the issue says ("a few cpu words") but helps out for actual codebases.
While reducing this, I found that `large_stack_arrays` was triggering for statically promoted arrays in constants/statics, so I also fixed that up as seen in the difference to [array_size_threshold.stderr](https://github.com/rust-lang/rust-clippy/compare/master...GnomedDev:rust-clippy:reduce-large-threshold?expand=1#diff-4c2a2a855d9ff7777f1d385be0c1bede2a3fc8aaab94837cde27a35235233fc7).
Closes #9449.
changelog: [`large_stack_arrays`]: No longer triggers in `static`/`const` context
changelog: [`large_const_arrays`]: Changed the default of [`array-size-threshold`] from `512kb` to `16kb`
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions