Point at `:` when using it instead of `;` When triggering type ascription in such a way that we can infer a statement end was intended, add a suggestion for the change. Always point out the reason for the expectation of a type is due to type ascription. Fix #42057, #41928. |
||
|---|---|---|
| .. | ||
| confuse-field-and-method | ||
| try-operator-on-main.rs | ||
| try-operator-on-main.stderr | ||
| tuple-float-index.rs | ||
| tuple-float-index.stderr | ||
| type-ascription-instead-of-statement-end.rs | ||
| type-ascription-instead-of-statement-end.stderr | ||
| type-ascription-with-fn-call.rs | ||
| type-ascription-with-fn-call.stderr | ||