| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2021-08-30 | `feature(const_generics)` -> `feature(const_param_types)` | lcnr | -29/+0 | |
| 2020-12-26 | update tests | Bastian Kauschke | -1/+0 | |
| 2020-10-12 | Bless expected errors | Ethan Brierley | -2/+2 | |
| 2020-10-11 | `min_const_generics` diagnostics improvements | Ethan Brierley | -2/+2 | |
| 2 3 | ||||
| 2020-10-03 | Replace "non trivial" with "non-trivial" | varkor | -2/+2 | |
| 2020-08-18 | change const param ty warning message | Bastian Kauschke | -1/+1 | |
| 2020-08-12 | Update stderr files | kadmin | -1/+1 | |
| And also fix some comments as suggested by lcnr | ||||
| 2020-08-12 | Add missing tests in root const-gen dir | kadmin | -4/+12 | |
| 2020-05-09 | adjust tests | Ralf Jung | -1/+1 | |
| 2020-01-21 | Make `TooGeneric` error in WF checking a proper error | varkor | -4/+3 | |
| `TooGeneric` is encountered during WF checking when we cannot determine that a constant involving a generic parameter will always be evaluated successfully (rather than resulting in an error). In these cases, the burden of proof should be with the caller, so that we can avoid post-monomorphisation tim errors (which was the previous previous behaviour). This commit ensures that this situation produces a proper compiler error, rather than silently ignoring it or ICEing. | ||||
| 2020-01-05 | Silence `TooGeneric` error | varkor | -0/+23 | |
| This error may be produced during intermediate failed attempts at evaluation of a generic const, which may nevertheless succeed later. | ||||
