<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/compiler/rustc_pattern_analysis/tests/intersection.rs, branch lcnr/rustc-dev-guide</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=lcnr/rustc-dev-guide</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=lcnr/rustc-dev-guide'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-07-20T16:27:30+00:00</updated>
<entry>
<title>pattern_analysis: add option to get a full set of witnesses</title>
<updated>2025-07-20T16:27:30+00:00</updated>
<author>
<name>Nadrieril</name>
<email>nadrieril+git@gmail.com</email>
</author>
<published>2025-07-19T09:28:31+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=2bb00741d463143a10e632bb118d4ed336dbb75f'/>
<id>urn:sha1:2bb00741d463143a10e632bb118d4ed336dbb75f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use `-Wunused_crate_dependencies` for compiler crates.</title>
<updated>2025-03-19T21:59:43+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2025-03-03T07:59:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=8121958fda43759fa94e3f74f7cdbb595ddcc0e5'/>
<id>urn:sha1:8121958fda43759fa94e3f74f7cdbb595ddcc0e5</id>
<content type='text'>
It's very useful. There are some false positives involving integration
tests in `rustc_pattern_analysis` and `rustc_serialize`. There is also a
false positive involving `rustc_driver_impl`'s
`rustc_randomized_layouts` feature. And I removed a `rustc_span` mention
in a doc comment in `rustc_log` because it wasn't integral to the
comment but caused a dev-dependency.
</content>
</entry>
<entry>
<title>Add `pattern_complexity_limit` to `Limits`.</title>
<updated>2025-02-16T22:30:33+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2025-02-06T23:57:14+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=b023671ce2019cdc1768d4acfb148c86ab70183a'/>
<id>urn:sha1:b023671ce2019cdc1768d4acfb148c86ab70183a</id>
<content type='text'>
It's similar to the other limits, e.g. obtained via `get_limit`. So it
makes sense to handle it consistently with the other limits. We now use
`Limit`/`usize` in most places instead of `Option&lt;usize&gt;`, so we use
`Limit::new(usize::MAX)`/`usize::MAX` to emulate how `None` used to work.

The commit also adds `Limit::unlimited`.
</content>
</entry>
<entry>
<title>Reformat using the new identifier sorting from rustfmt</title>
<updated>2024-09-22T23:11:29+00:00</updated>
<author>
<name>Michael Goulet</name>
<email>michael@errs.io</email>
</author>
<published>2024-09-22T23:05:04+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c682aa162b0d41e21cc6748f4fecfe01efb69d1f'/>
<id>urn:sha1:c682aa162b0d41e21cc6748f4fecfe01efb69d1f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Reformat `use` declarations.</title>
<updated>2024-07-28T22:26:52+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2024-07-28T22:13:50+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=84ac80f1921afc243d71fd0caaa4f2838c294102'/>
<id>urn:sha1:84ac80f1921afc243d71fd0caaa4f2838c294102</id>
<content type='text'>
The previous commit updated `rustfmt.toml` appropriately. This commit is
the outcome of running `x fmt --all` with the new formatting options.
</content>
</entry>
<entry>
<title>Add some tests</title>
<updated>2024-07-24T06:02:55+00:00</updated>
<author>
<name>Nadrieril</name>
<email>nadrieril+git@gmail.com</email>
</author>
<published>2024-07-21T12:37:10+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c4d6a4a7e4d8d006f6d08345e91fb1cdf0fc7e7a'/>
<id>urn:sha1:c4d6a4a7e4d8d006f6d08345e91fb1cdf0fc7e7a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add blank lines after module-level `//!` comments.</title>
<updated>2024-06-19T23:23:20+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2024-06-19T19:04:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=665821cb606076bcf159c47e3e8e72a14fa512e3'/>
<id>urn:sha1:665821cb606076bcf159c47e3e8e72a14fa512e3</id>
<content type='text'>
Most modules have such a blank line, but some don't. Inserting the blank
line makes it clearer that the `//!` comments are describing the entire
module, rather than the `use` declaration(s) that immediately follows.
</content>
</entry>
<entry>
<title>Add a crate-custom test harness</title>
<updated>2024-03-19T01:22:43+00:00</updated>
<author>
<name>Nadrieril</name>
<email>nadrieril+git@gmail.com</email>
</author>
<published>2024-03-04T15:57:32+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=d697dd44d18fbab9a28032d7b1ceba829600637e'/>
<id>urn:sha1:d697dd44d18fbab9a28032d7b1ceba829600637e</id>
<content type='text'>
</content>
</entry>
</feed>
