-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better error message when struct construction field name is left "implicit" #4909
Comments
Not critical for 0.7. Nominating for milestone 5, production-ready |
accepted for production ready |
Still present, still just about as unpleasant an error message. |
assigning P-low. |
In the latest master (e2273d9), this looks to be fixed: struct Foo {
A: int,
B: int
}
fn main() {
let x = Foo{A:1};
}
|
@eminence your example does not reflect what the bug report is asking about. Here is variant of your example that illustrates the problem in the description (which I will also add to the bug description after I finish typing this comment): http://is.gd/GDjwLK (also updated title to better reflect the description) |
ah, my apologies -- I did not properly understand the reported issue. thanks for the clarification. |
visiting for triage The error message has not changed for the original code example, so this issue is still valid |
Current message:
Are these two together clear enough? |
That seems like a good enough improvement to me. |
(Updated with concrete example:)
yields (live playpen: http://is.gd/GDjwLK)
This feels like something we should be able to better report (possibly as a note suggestion).
Original bug report follows:
This feels like something we should be able to better report (possibly as a note suggestion).
The text was updated successfully, but these errors were encountered: