León Orell Valerian Liehr

[WIP] [crater-only] Make a watered-down version of lazy type aliases the default

2

Not ready for crater yet since this patch can't build stage1 std at the moment :smiling_face_with_tear:, still need to figure that out. I've at least managed to make it build...

Fix type resolution of associated const equality bounds (take 2)

17

Instead of trying to re-resolve the type of assoc const bindings inside the `type_of` query impl in an incomplete manner, transfer the already (correctly) resolved type from `add_predicates_for_ast_type_binding` to `type_of`/`anon_type_of`...

[Proof of concept] Recover from struct literals with placeholder path

1

I'm surprised my naive approach seems to work but it feels more than hacky (skipping name resolution entirely). I hope to gather some feedback for how to make this more...

`tests/rustdoc/line-breaks.rs` had several issues: 1. It used `//@count` instead of `// @count` (notice the space!) which gets treated as a `ui_test` directive instead of a `htmldocck` one. `compiletest` didn't flag...

Reject overly generic assoc const binding types

1

Split off from #119385 to make #119385 easier to review. --- In the *instantiated* type of assoc const bindings 1. reject **early-bound generic params** * Provide a rich error message...

Treat weak alias types more like ADTs when computing implied bounds

1

For context, we want to treat lazy type aliases / weak alias types just like ADTs when computing implied bounds (#118479, T-lang design meeting 2023-11-09) but the way I've implemented...

Normalize trait ref before orphan check & consider ty params in alias types to be uncovered

52

Fixes #99554, fixes rust-lang/types-team#104. Supersedes #100555. r? lcnr

This code crashes the compiler: ```funky func foo : a = switch 0 case foozle func bar : Int = 0 ``` With this error message: ``` panic: runtime error:...

If you use keywords (`func`, `alias`, `record`, `union`) in places where identifiers are expected, the compiler does not give a reasonable report but crashes. Faulty inputs might look like: `alias...

Per definition, the literal `0` is of type `Int` and the literal `0.0` is of type `Float`. Thus, both lines below correctly fail to type-check: ```funky (self : Int ->...