about summary refs log tree commit diff
path: root/tests/rustdoc-js-std/parser-slice-array.js
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-03-05 19:53:18 +0100
committerGitHub <noreply@github.com>2024-03-05 19:53:18 +0100
commit640648b8932aa094b746c0de7012c7d2bd9955e8 (patch)
tree1dd2527c92b684bbf0488da742f045b1ab510f1b /tests/rustdoc-js-std/parser-slice-array.js
parent96561a8fd134e8f2b205769a4fca03b392d9f484 (diff)
parent9d9b26bca942dc4cf9cda0b8612bff715aebf7da (diff)
downloadrust-640648b8932aa094b746c0de7012c7d2bd9955e8.tar.gz
rust-640648b8932aa094b746c0de7012c7d2bd9955e8.zip
Rollup merge of #121202 - Urgau:check-cfg-limit-diagnostics, r=pnkfelix
Limit the number of names and values in check-cfg diagnostics

The Rust for Linux [feedback](https://github.com/rust-lang/rust/issues/82450#issuecomment-1947462977) to the check-cfg Call for Testing, revealed a weakness in the check-cfg. They are unbounded and in the case RfL they have ~20k cfgs and having them printed (even once) is unbearable.

This PR limits it to 35 (28 rustc well known + `feature` + `docsrs` + 5 custom) which feels like a good middle ground for regular users (i.e. Cargo users).

When it goes over that limit print the N first with " and X more".

``@rustbot`` label +F-check-cfg
Diffstat (limited to 'tests/rustdoc-js-std/parser-slice-array.js')
0 files changed, 0 insertions, 0 deletions