Thijs Molendijk

Using `method`s as standalone expressions result in misleading error message when type checking is enabled

1

Since `method`s are technically expressions, they're allowed to appear in expression positions. It looks like the type checker has no support for them, yielding a `"checking for s-method not implemented"`/`"synthesis...

Certain invalid `forall`/type application combinations result in an unmatched cases in the type checker (4 fields)

1

Simplest example I could find: ``` type Bool = Boolean type Id = T type AlsoBool = Id # Matching a cases branch pattern errored. a :: AlsoBool = 1...

`check`ing of template expressions with an expected projected type results in an unmatched cases

1

I'd expect the following to typecheck (given that `...` can produce any value), but it instead results in the classic "Missing a cases branch pattern errored."): ``` type Id =...

So here's a large PR that is partially a rewrite of the removal reasons module and partially a proof of concept of the removal reasons. It's quite some spaghetti, so...

Confusing rustc error message on generic struct with misleading suggestion

1

I have the following: ```rust #[derive(Debug, BinRead)] pub struct Array where T: for = ()>, { _count: u32, #[br(count = _count)] pub data: Vec, } ``` For this, rustc complains...

When I have item frames placed in 1.7 (with maps in them), it works fine for players on 1.7.2 and 1.7.4. But, whenever a user on 1.6.2 comes close (within...