Florian Diebold

Ambiguity through unrelated env clauses because of implied bounds

1

This comes from https://github.com/rust-analyzer/rust-analyzer/issues/10653, basically the example is this: ```rust fn foo() where A: IntoIterator, B: IntoIterator, { let _x: ::Item; } ``` We'd expect `_x` to have type `u32`...

Add binders validator

3

This is a visitor which checks that all bound vars refer to an existing binder of the right type. This has been quite useful for me: we somewhat regularly have...

Ambiguity problems with associated types

17

While handling associated types in rust-analyzer, I ran into two problems that I want to ask about. These are probably not related, so I can split this up if necessary,...

Prefer clauses from the environment

5

The following code compiles in rustc: ```rust fn f(u: T) { let x = u.into(); x.as_str(); } ``` This works even though there are other (blanket) impls that could apply...

This is a: - [X] Bug Report Which concerns: - [X] babel-plugin-flow-runtime --- ### What is the current behaviour? 1. When warnings are enabled via the options, `@flow-runtime assert` does...

Improve syntax fixup for proc macros

1

To make completion work inside attribute proc macros like `#[tokio::main]`, we take incomplete code inside the attribute input and 'fix it up' to make sure the proc macro can parse...

Don't apply Rust function snippet logic if rust-analyzer is used

1

rust-analyzer has better server-side logic, and in fact this fallback logic only applied when it was undesirable (e.g. when importing functions), because that's when RA doesn't return a snippet.

Handling EofException

7

This is an issue where I'm not 100% sure what part of the stack is really responsible for the problem, so I'll just start here. We have an API using...

GAT support

8

Since generic associated types are on their way to stabilization, we'll need to start looking into implementing them :sweat_smile:

Bad trait solving performance with bounds on associated types

1

A bound like `T::Item: Debug` can slow down trait solving a lot because it will currently result in a search through all `Debug` impls ([this case](https://github.com/rust-analyzer/rust-analyzer/blob/86d3b784075966028c84e24ff4327a26fe7fbacb/crates/hir_ty/src/traits/chalk.rs#L116) will be hit), see...