<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/ui/structs, branch beta</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=beta</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=beta'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2025-09-13T07:26:02+00:00</updated>
<entry>
<title>Rollup merge of #145896 - Oneirical:uncountable-integer-10, r=jieyouxu</title>
<updated>2025-09-13T07:26:02+00:00</updated>
<author>
<name>Jacob Pratt</name>
<email>jacob@jhpratt.dev</email>
</author>
<published>2025-09-13T07:26:02+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=82bb6d523bf3b1e6cd8d160565ab18d01640a4dd'/>
<id>urn:sha1:82bb6d523bf3b1e6cd8d160565ab18d01640a4dd</id>
<content type='text'>
Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [#3 of Batch #2]

Part of rust-lang/rust#133895

Methodology:

1. Refer to the previously written `tests/ui/SUMMARY.md`
2. Find an appropriate category for the test, using the original issue thread and the test contents.
3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers)
4. Rename the tests to make their purpose clearer

Inspired by the methodology that `@Kivooeo` was using.

r? `@jieyouxu`
</content>
</entry>
<entry>
<title>Add test batch 3</title>
<updated>2025-09-12T18:45:12+00:00</updated>
<author>
<name>Oneirical</name>
<email>manchot@videotron.ca</email>
</author>
<published>2025-08-20T18:02:50+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=957fa10d50787a4c6c6d8a35be5af6bd43ba1770'/>
<id>urn:sha1:957fa10d50787a4c6c6d8a35be5af6bd43ba1770</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rollup merge of #145676 - Oneirical:uncountable-integer-9, r=jieyouxu</title>
<updated>2025-08-29T10:37:30+00:00</updated>
<author>
<name>Matthias Krüger</name>
<email>476013+matthiaskrgr@users.noreply.github.com</email>
</author>
<published>2025-08-29T10:37:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=47f1df5ca35217ca5e21ffd1f1daa3cb623470e2'/>
<id>urn:sha1:47f1df5ca35217ca5e21ffd1f1daa3cb623470e2</id>
<content type='text'>
Rehome 30 `tests/ui/issues/` tests to other subdirectories under `tests/ui/` [#2 of Batch #2]

Part of rust-lang/rust#133895

Methodology:

1. Refer to the previously written `tests/ui/SUMMARY.md`
2. Find an appropriate category for the test, using the original issue thread and the test contents.
3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers)
4. Rename the tests to make their purpose clearer

Inspired by the methodology that `@Kivooeo` was using.

r? `@jieyouxu`
</content>
</entry>
<entry>
<title>Add test batch 2</title>
<updated>2025-08-27T19:06:05+00:00</updated>
<author>
<name>Oneirical</name>
<email>manchot@videotron.ca</email>
</author>
<published>2025-08-20T18:02:44+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=2dc4638c4637bf8ddb83577535317dad21abdf6d'/>
<id>urn:sha1:2dc4638c4637bf8ddb83577535317dad21abdf6d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add test batch 1</title>
<updated>2025-08-27T04:23:26+00:00</updated>
<author>
<name>Oneirical</name>
<email>manchot@videotron.ca</email>
</author>
<published>2025-08-20T18:02:39+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=2e659f58940a31fa625e88f75f78111ed773f32d'/>
<id>urn:sha1:2e659f58940a31fa625e88f75f78111ed773f32d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Rehome tests/ui/issues/ tests [5/?]</title>
<updated>2025-08-17T17:01:02+00:00</updated>
<author>
<name>Oneirical</name>
<email>manchot@videotron.ca</email>
</author>
<published>2025-07-13T20:56:31+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=75e0263af9ca27eac2c922538582deec764d1e7b'/>
<id>urn:sha1:75e0263af9ca27eac2c922538582deec764d1e7b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Do not ICE on private type in field of unresolved struct</title>
<updated>2025-08-14T15:59:32+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2025-08-13T18:43:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=caadc8df3519f1c92ef59ea816eb628345d9f52a'/>
<id>urn:sha1:caadc8df3519f1c92ef59ea816eb628345d9f52a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Auto merge of #135846 - estebank:non-exhaustive-dfv-ctor-2, r=BoxyUwU</title>
<updated>2025-08-10T23:47:25+00:00</updated>
<author>
<name>bors</name>
<email>bors@rust-lang.org</email>
</author>
<published>2025-08-10T23:47:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=21a19c297d4f5a03501d92ca251bd7a17073c08a'/>
<id>urn:sha1:21a19c297d4f5a03501d92ca251bd7a17073c08a</id>
<content type='text'>
Detect struct construction with private field in field with default

When trying to construct a struct that has a public field of a private type, suggest using `..` if that field has a default value.

```
error[E0603]: struct `Priv1` is private
  --&gt; $DIR/non-exhaustive-ctor-2.rs:19:39
   |
LL |     let _ = S { field: (), field1: m::Priv1 {} };
   |                            ------     ^^^^^ private struct
   |                            |
   |                            while setting this field
   |
note: the struct `Priv1` is defined here
  --&gt; $DIR/non-exhaustive-ctor-2.rs:14:4
   |
LL |    struct Priv1 {}
   |    ^^^^^^^^^^^^
help: the type `Priv1` of field `field1` is private, but you can construct the default value defined for it in `S` using `..` in the struct initializer expression
   |
LL |     let _ = S { field: (), .. };
   |                            ~~
```
</content>
</entry>
<entry>
<title>Rollup merge of #144553 - Oneirical:uncountable-integer-4, r=jieyouxu</title>
<updated>2025-08-10T19:43:52+00:00</updated>
<author>
<name>Jacob Pratt</name>
<email>jacob@jhpratt.dev</email>
</author>
<published>2025-08-10T19:43:52+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=5bd4e832d3608a4b06e3bc0b0bf348e664e961ec'/>
<id>urn:sha1:5bd4e832d3608a4b06e3bc0b0bf348e664e961ec</id>
<content type='text'>
Rehome 32 `tests/ui/issues/` tests to other subdirectories under `tests/ui/`

rust-lang/rust#143902 divided into smaller, easier to review chunks.

Part of rust-lang/rust#133895

Methodology:

1. Refer to the previously written `tests/ui/SUMMARY.md`
2. Find an appropriate category for the test, using the original issue thread and the test contents.
3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers)
4. Rename the tests to make their purpose clearer

Inspired by the methodology that `@Kivooeo` was using.

r? `@jieyouxu`
</content>
</entry>
<entry>
<title>Detect struct construction with private field in field with default</title>
<updated>2025-08-10T19:15:18+00:00</updated>
<author>
<name>Esteban Küber</name>
<email>esteban@kuber.com.ar</email>
</author>
<published>2025-01-21T21:07:20+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=464a6b1b4af28f7b2d1adf051bad3f182e23b88e'/>
<id>urn:sha1:464a6b1b4af28f7b2d1adf051bad3f182e23b88e</id>
<content type='text'>
When trying to construct a struct that has a public field of a private type, suggest using `..` if that field has a default value.

```
error[E0603]: struct `Priv1` is private
  --&gt; $DIR/non-exhaustive-ctor.rs:25:39
   |
LL |     let _ = S { field: (), field1: m::Priv1 {} };
   |                            ------     ^^^^^ private struct
   |                            |
   |                            while setting this field
   |
note: the struct `Priv1` is defined here
  --&gt; $DIR/non-exhaustive-ctor.rs:14:4
   |
LL |    struct Priv1 {}
   |    ^^^^^^^^^^^^
help: the field `field1` you're trying to set has a default value, you can use `..` to use it
   |
LL |     let _ = S { field: (), .. };
   |                            ~~
```
</content>
</entry>
</feed>
