https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try 2025-05-22T17:31:28+00:00 2025-05-22T17:31:28+00:00 binarycat binarycat@envs.net 2025-02-01T19:35:06+00:00 urn:sha1:3005a09fedd5c874c36ca1c788954e51e3fa0617 1. rustdoc::bare_urls doesn't output invalid suggestions if source_span_for_markdown_range fails to find a span 2. source_span_for_markdown_range tries harder to return a span by applying an additional diagnostic fixes https://github.com/rust-lang/rust/issues/135851 2024-12-13T18:48:33+00:00 Esteban Küber esteban@kuber.com.ar 2024-12-13T18:18:19+00:00 urn:sha1:9f1044ef76de2ae88ac5c38a27b2bd49f5507d94 Don't consider `///` and `//!` docstrings to be empty for the purposes of multiline span rendering. 2024-12-12T23:36:27+00:00 Esteban Küber esteban@kuber.com.ar 2024-12-11T21:48:33+00:00 urn:sha1:49a22a4245bd6dfd3646a6658e0f90a2ab0657ad 2024-12-12T23:36:27+00:00 Esteban Küber esteban@kuber.com.ar 2024-12-11T21:17:33+00:00 urn:sha1:65a54a7f277b30ebeeacb5b303804fa8ffb5c922 Consider comments and bare delimiters the same as an "empty line" for purposes of hiding rendered code output of long multispans. This results in more aggressive shortening of rendered output without losing too much context, specially in `*.stderr` tests that have "hidden" comments. 2024-11-29T06:23:34+00:00 Nicholas Nethercote n.nethercote@gmail.com 2024-11-25T02:15:28+00:00 urn:sha1:d626f6a2f4b8f44f661ba76d1b5b67c4d7826df9 This is in a test where the arrangement of backticks matters, but the exact words do not. 2024-03-29T20:31:35+00:00 Michael Howell michael@notriddle.com 2024-03-29T19:31:34+00:00 urn:sha1:98642da6a9dda39e711b7f3520b0b6d40c1cd043 2024-01-30T21:25:29+00:00 Nicholas Nethercote n.nethercote@gmail.com 2024-01-30T05:57:29+00:00 urn:sha1:4225a1e186afe39c1ae81c5065d24287d6d49fb9 `Diagnostic::keys`, which is used for hashing and equating diagnostics, has a surprising behaviour: it ignores children, but only for lints. This was added in #88493 to fix some duplicated diagnostics, but it doesn't seem necessary any more. This commit removes the special case and only four tests have changed output, with additional errors. And those additional errors aren't exact duplicates, they're just similar. For example, in src/tools/clippy/tests/ui/same_name_method.rs we currently have this error: ``` error: method's name is the same as an existing method in a trait --> $DIR/same_name_method.rs:75:13 | LL | fn foo() {} | ^^^^^^^^^^^ | note: existing `foo` defined here --> $DIR/same_name_method.rs:79:9 | LL | impl T1 for S {} | ^^^^^^^^^^^^^^^^ ``` and with this change we also get this error: ``` error: method's name is the same as an existing method in a trait --> $DIR/same_name_method.rs:75:13 | LL | fn foo() {} | ^^^^^^^^^^^ | note: existing `foo` defined here --> $DIR/same_name_method.rs:81:9 | LL | impl T2 for S {} | ^^^^^^^^^^^^^^^^ ``` I think printing this second argument is reasonable, possibly even preferable to hiding it. And the other cases are similar. 2023-12-01T22:01:19+00:00 Nicholas Nethercote n.nethercote@gmail.com 2023-11-30T04:01:11+00:00 urn:sha1:5d1d3844430923395d38159c8979e587a1ca2879 Because the corresponding `Level` is `DelayedBug` and `span_delayed_bug` follows the pattern used everywhere else: `span_err`, `span_warning`, etc. 2023-10-05T01:04:41+00:00 Alex Macleod alex@macleod.io 2023-10-04T18:34:50+00:00 urn:sha1:5453a9f34d21bdd1031d58b68fcd6a92adc82108 2023-08-18T07:31:32+00:00 Kyle Lin minecraft.kyle.train@gmail.com 2023-07-03T18:40:05+00:00 urn:sha1:62113f6657d91ba294abe96852c25c1c4eb4c501