<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/ui/unpretty/exhaustive.rs, branch automation/bors/try</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=automation/bors/try'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-08-21T21:57:52+00:00</updated>
<entry>
<title>Rollup merge of #145604 - compiler-errors:static-closure, r=fmease</title>
<updated>2025-08-21T21:57:52+00:00</updated>
<author>
<name>Jacob Pratt</name>
<email>jacob@jhpratt.dev</email>
</author>
<published>2025-08-21T21:57:52+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=f49d69093ec31583b055615bb07e056fc9fc0ee3'/>
<id>urn:sha1:f49d69093ec31583b055615bb07e056fc9fc0ee3</id>
<content type='text'>
Gate static closures behind a parser feature

I'd like to gate `static ||` closures behind a feature gate, since we shouldn't allow people to take advantage of this syntax if it's currently unstable. Right now, since it's only rejected after ast lowering, it's accessible to macros.

Let's crater this to see if we can claw it back without breaking anyone's code.
</content>
</entry>
<entry>
<title>Gate static coroutines behind a parser feature</title>
<updated>2025-08-19T13:12:31+00:00</updated>
<author>
<name>Michael Goulet</name>
<email>michael@errs.io</email>
</author>
<published>2025-08-19T13:12:17+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=db0c825d2c745fdf87edd501ebda222052f98771'/>
<id>urn:sha1:db0c825d2c745fdf87edd501ebda222052f98771</id>
<content type='text'>
</content>
</entry>
<entry>
<title>resolve prelude import at `build_reduced_graph` phase</title>
<updated>2025-08-14T13:28:35+00:00</updated>
<author>
<name>LorrensP-2158466</name>
<email>lorrens.pantelis@student.uhasselt.be</email>
</author>
<published>2025-08-11T20:33:12+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=ff560d3c9a662786ab1126b32320cc7cb0169678'/>
<id>urn:sha1:ff560d3c9a662786ab1126b32320cc7cb0169678</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove support for dyn*</title>
<updated>2025-07-01T19:00:21+00:00</updated>
<author>
<name>Michael Goulet</name>
<email>michael@errs.io</email>
</author>
<published>2025-06-26T02:01:38+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=2516c339829cd9193c15464218a981b8547157ca'/>
<id>urn:sha1:2516c339829cd9193c15464218a981b8547157ca</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rollup merge of #139858 - oli-obk:new-const-traits-syntax, r=fee1-dead</title>
<updated>2025-06-27T20:13:00+00:00</updated>
<author>
<name>Matthias Krüger</name>
<email>476013+matthiaskrgr@users.noreply.github.com</email>
</author>
<published>2025-06-27T20:13:00+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=36c2b011cb4bb9bd34647486551e85a969773c8d'/>
<id>urn:sha1:36c2b011cb4bb9bd34647486551e85a969773c8d</id>
<content type='text'>
New const traits syntax

This PR only affects the AST and doesn't actually change anything semantically.

All occurrences of `~const` outside of libcore have been replaced by `[const]`. Within libcore we have to wait for rustfmt to be bumped in the bootstrap compiler. This will happen "automatically" (when rustfmt is run) during the bootstrap bump, as rustfmt converts `~const` into `[const]`. After this we can remove the `~const` support from the parser

Caveat discovered during impl: there is no legacy bare trait object recovery for `[const] Trait` as that snippet in type position goes down the slice /array parsing code and will error

r? ``@fee1-dead``

cc ``@nikomatsakis`` ``@traviscross`` ``@compiler-errors``
</content>
</entry>
<entry>
<title>Change const trait bound syntax from ~const to [const]</title>
<updated>2025-06-26T13:46:45+00:00</updated>
<author>
<name>Oli Scherer</name>
<email>github333195615777966@oli-obk.de</email>
</author>
<published>2025-03-11T12:08:45+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=eb7245a864613f290c5668f4f4e8376edd065dc6'/>
<id>urn:sha1:eb7245a864613f290c5668f4f4e8376edd065dc6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Migrate some tests away from `concat-idents`</title>
<updated>2025-06-24T10:54:54+00:00</updated>
<author>
<name>Trevor Gross</name>
<email>tmgross@umich.edu</email>
</author>
<published>2025-06-19T06:12:22+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=f8ab9343b8e6f195be036bdd99884c8721876820'/>
<id>urn:sha1:f8ab9343b8e6f195be036bdd99884c8721876820</id>
<content type='text'>
`concat_idents!` is in the process of being removed, but a few things it
is used to test will still be relevant. Migrate these tests to something
other than `concat_idents`.
</content>
</entry>
<entry>
<title>Improve coverage of HIR pretty printing.</title>
<updated>2025-05-02T02:41:02+00:00</updated>
<author>
<name>Nicholas Nethercote</name>
<email>n.nethercote@gmail.com</email>
</author>
<published>2025-04-29T05:24:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=3f842e51a6e97dad23f9717ae27db2960dde1c34'/>
<id>urn:sha1:3f842e51a6e97dad23f9717ae27db2960dde1c34</id>
<content type='text'>
By taking the existing `expanded-exhaustive.rs` test and running it with
both `Zunpretty=expanded` *and* `Zunpretty=hir`.

Also rename some files, and split the asm parts out so they only run on
x86-64.
</content>
</entry>
</feed>
