Add suggestion for incorrect field syntax.#57863
Conversation
|
Sorry for another addition to your review queue @estebank. Not sure if this is the approach we want to take with this issue or if it is too large a change for the potential gain - if we just want to change to keep the existing error but add |
93b7b25 to
ef261e0
Compare
ef261e0 to
517840b
Compare
|
@bors r+ |
|
📌 Commit 517840b3124c859bdfcd5e3d0ec8666d036dcb9f has been approved by |
|
@bors r- |
517840b to
ac0d342
Compare
I leant toward matching the structure of the existing messages - |
|
I just feel this might sound like a piece of the error is missing, but it's not a big deal, especially if this is an existing convention for singular items (in which case it might be a better idea to potentially adjust the convention). |
|
Yeah, sorry about that it was my typo, my bad. It should be "expected |
This commit adds a suggestion when a `=` character is used when specifying the value of a field in a struct constructor incorrectly instead of a `:` character.
ac0d342 to
f14d007
Compare
|
@estebank should be fixed now. |
|
@bors r+ |
|
📌 Commit f14d007 has been approved by |
Add suggestion for incorrect field syntax. Fixes rust-lang#57684. This commit adds a suggestion when a `=` character is used when specifying the value of a field in a struct constructor incorrectly instead of a `:` character. r? @estebank
Add suggestion for incorrect field syntax. Fixes rust-lang#57684. This commit adds a suggestion when a `=` character is used when specifying the value of a field in a struct constructor incorrectly instead of a `:` character. r? @estebank
Rollup of 9 pull requests Successful merges: - #57380 (Fix Instant/Duration math precision & associativity on Windows) - #57606 (Get rid of the fake stack frame for reading from constants) - #57803 (Several changes to libunwind for SGX target) - #57846 (rustdoc: fix ICE from loading proc-macro stubs) - #57860 (Add os::fortanix_sgx::ffi module) - #57861 (Don't export table by default in wasm) - #57863 (Add suggestion for incorrect field syntax.) - #57867 (Fix std::future::from_generator documentation) - #57873 (Stabilize no_panic_pow) Failed merges: r? @ghost
Fixes #57684.
This commit adds a suggestion when a
=character is used whenspecifying the value of a field in a struct constructor incorrectly
instead of a
:character.r? @estebank