| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-11-24 | Show number in error message even for one error | Nilstrieb | -4/+4 | |
| Co-authored-by: Adrian <adrian.iosdev@gmail.com> | ||||
| 2023-11-13 | review comments: more targeted span setting approach | Esteban Küber | -0/+2 | |
| 2023-11-13 | Always point at index span on index obligation failure | Esteban Küber | -0/+20 | |
| Use more targetted span for index obligation failures by rewriting the obligation cause span. CC #66023 | ||||
| 2023-10-02 | Point out the actual mismatch error | Michael Goulet | -0/+2 | |
| 2023-10-02 | For a single impl candidate, try to unify it with error trait ref | Michael Goulet | -2/+2 | |
| 2023-08-04 | Improve spans for indexing expressions | Nilstrieb | -0/+115 | |
| Indexing is similar to method calls in having an arbitrary left-hand-side and then something on the right, which is the main part of the expression. Method calls already have a span for that right part, but indexing does not. This means that long method chains that use indexing have really bad spans, especially when the indexing panics and that span in coverted into a panic location. This does the same thing as method calls for the AST and HIR, storing an extra span which is then put into the `fn_span` field in THIR. | ||||
