| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-04-19 | Emit specific error for struct literal in conditions | Esteban Küber | -39/+15 | |
| 2019-03-22 | Reword type ascription note to reduce verbosity | Esteban Küber | -12/+2 | |
| 2019-03-22 | Review comment | Esteban Küber | -2/+2 | |
| 2019-03-22 | Expand suggestions for type ascription parse errors | Esteban Küber | -0/+26 | |
| 2019-03-11 | Update tests | Vadim Petrochenkov | -1/+1 | |
| 2019-01-18 | Rollup merge of #57725 - estebank:parens, r=michaelwoerister | Mazdak Farrokhzad | -3/+9 | |
| Use structured suggestion to surround struct literal with parenthesis | ||||
| 2019-01-17 | Use structured suggestion to surround struct literal with parenthesis | Esteban Küber | -3/+9 | |
| 2019-01-09 | clarify resolve typo suggestion | Andy Russell | -1/+1 | |
| Include the kind of the binding that we're suggesting, and use a structured suggestion. | ||||
| 2018-12-25 | Remove licenses | Mark Rousskov | -7/+7 | |
| 2018-06-04 | Suggest braces when a struct literal needs them | Esteban Küber | -2/+41 | |
| When writing a struct literal in an expression that expects a block to be started afterwards (like an `if` statement), do not suggest using the same struct literal: ``` did you mean `S { /* fields * /}`? ``` Instead, suggest surrounding the expression with parentheses: ``` did you mean `(S { /* fields * /})`? ``` | ||||
| 2018-03-14 | update tests | Guillaume Gomez | -1/+1 | |
| 2018-02-26 | Update UI tests | Vadim Petrochenkov | -1/+1 | |
| 2018-02-25 | Update ui tests | Guillaume Gomez | -0/+1 | |
| 2018-02-08 | Move some E0XXX to `ui` | Esteban Küber | -0/+8 | |
