Esteban Küber
4be07075b3
Tweak message on ADT with private fields building
...
When trying to create an inaccessible ADT due to private fields, handle
the case when no fields were passed.
```
error: cannot construct `Foo` with struct literal syntax due to private fields
--> $DIR/issue-76077.rs:8:5
|
LL | foo::Foo {};
| ^^^^^^^^
|
= note: private field `you_cant_use_this_field` that was not provided
```
2023-11-29 18:11:57 +00:00
Esteban Küber
4d16171f56
Account for number of arguments in suggestion
2023-11-19 17:50:47 +00:00
Esteban Küber
69edf8e784
Suggest Default::default() for struct literals with private fields
2023-11-19 17:50:47 +00:00
Esteban Küber
be0958f5ab
Suggest builder functions on struct literal with private fields
2023-11-19 17:50:47 +00:00
Esteban Küber
987155f35d
Suggest using builder on curly brace struct called as fn
2023-11-19 17:50:46 +00:00
Esteban Küber
a4f47de7ff
On private tuple struct, suggest Default::default when possible
2023-11-19 17:50:46 +00:00
Esteban Küber
42aa1273b0
When encountering struct fn call literal with private fields, suggest all builders
...
When encountering code like `Box(42)`, suggest `Box::new(42)` and *all*
other associated functions that return `-> Box<T>`.
2023-11-19 17:47:41 +00:00
Esteban Küber
87dc85d322
Suggest assoc fn new when trying to build tuple struct with private fields
...
Fix #22488 .
2023-10-26 22:21:05 +00:00
