| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2019-02-21 | Add address stability test for matches | Matthew Jasper | -0/+39 | |
| 2019-02-08 | review comments: (marginally) reduce memory consumtion | Esteban Küber | -1/+41 | |
| 2019-02-07 | Add test for type mismatch on first match arm | Esteban Küber | -0/+58 | |
| 2019-01-14 | Auto merge of #57387 - euclio:nonstandard-style-suggestions, r=oli-obk | bors | -77/+0 | |
| Use structured suggestions for nonstandard style lints This PR modifies the lints in the nonstandard_style group to use structured suggestions. Note that there's a bit of tricky span calculation going on for the `crate_name` attribute. It also simplifies the code a bit: I don't think the "fallback" suggestions for these lints can actually be triggered. Fixes #48103. Fixes #52414. | ||||
| 2019-01-12 | Don't add label to the match expr when the type is not fully realized | Esteban Küber | -2/+0 | |
| 2019-01-12 | Reword label as per review comment | Esteban Küber | -3/+3 | |
| 2019-01-12 | Point at the match discriminant when arm pattern has a type mismatch | Esteban Küber | -1/+7 | |
| 2019-01-08 | improve non_upper_case_globals diagnostics | Andy Russell | -77/+0 | |
| Use a structured suggestion and tighten the span to just the identifier. | ||||
| 2018-12-31 | Improve type mismatch error messages | Yuning Zhang | -1/+1 | |
| Replace "integral variable" with "integer" and replace "floating-point variable" with "floating-point number" to make the message less confusing. | ||||
| 2018-12-25 | Remove licenses | Mark Rousskov | -347/+76 | |
| 2018-12-24 | make non_camel_case_types an early lint | Andy Russell | -41/+37 | |
| 2018-11-30 | Fix bug in matching on floating-point ranges | varkor | -7/+1 | |
| 2018-11-30 | Update existing tests with more precise error messages | varkor | -3/+9 | |
| 2018-11-07 | fix ICE | F001 | -0/+27 | |
| 2018-10-20 | Auto merge of #55119 - varkor:unwarned-match-on-never, r=nikomatsakis | bors | -30/+0 | |
| Allow explicit matches on ! without warning It's now possible to explicitly match on `!` without an unreachable code warning. This seems desirable as promoting explicitness. Fixes https://github.com/rust-lang/rust/issues/55116. | ||||
| 2018-10-17 | Update output for borrowck=migrate compare mode. | David Wood | -25/+0 | |
| This commit updates the test output for the updated NLL compare mode that uses `-Z borrowck=migrate` rather than `-Z borrowck=mir`. The previous commit changes `compiletest` and this commit only updates `.nll.stderr` files. | ||||
| 2018-10-16 | Remove outdated test | varkor | -30/+0 | |
| 2018-09-01 | Update tests | Basile Desloges | -12/+0 | |
| 2018-08-25 | Use smaller span for adjustments on block expressions | Matthew Jasper | -21/+15 | |
| 2018-08-14 | Update former compile-fail tests | Matthew Jasper | -2/+2 | |
| 2018-08-14 | Merged migrated compile-fail tests and ui tests. Fixes #46841. | David Wood | -0/+1493 | |
