rust/tests/ui/type-inference
Esteban Küber 796be88062 Use `fn` ptr signature instead of `{closure@..}` in infer error
When suggesting a type on inference error, do not use `{closure@..}`.
Instead, replace with an appropriate `fn` ptr.

On the error message, use `short_ty_string` and write long types to
disk.

```
error[E0284]: type annotations needed for `Select<{closure@lib.rs:2782:13}, _, Expression<'_>, _>`
  --> crates/lang/src/parser.rs:41:13
   |
41 |         let lit = select! {
   |             ^^^
42 |             Token::Int(i) = e => Expression::new(Expr::Lit(ast::Lit::Int(i.parse().unwrap())), e.span()),
   |                                                                                                  ---- type must be known at this point
   |
   = note: the full type name has been written to '/home/gh-estebank/iowo/target/debug/deps/lang-e2d6e25819442273.long-type-4587393693885174369.txt'
   = note: cannot satisfy `<_ as chumsky::input::Input<'_>>::Span == SimpleSpan`
help: consider giving `lit` an explicit type, where the type for type parameter `I` is specified
   |
41 |         let lit: Select<for<'a, 'b> fn(tokens::Token<'_>, &'a mut MapExtra<'_, 'b, _, _>) -> Option<Expression<'_>>, _, Expression<'_>, _> = select! {
   |                +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
```

instead of

```
error[E0284]: type annotations needed for `Select<{closure@/home/gh-estebank/.cargo/registry/src/index.crates.io-6f17d22bba15001f/chumsky-1.0.0-alpha.6/src/lib.rs:2782:13: 2782:28}, _, Expression<'_>, _>`
  --> crates/lang/src/parser.rs:41:13
   |
41 |         let lit = select! {
   |             ^^^
42 |             Token::Int(i) = e => Expression::new(Expr::Lit(ast::Lit::Int(i.parse().unwrap())), e.span()),
   |                                                                                                  ---- type must be known at this point
   |
   = note: cannot satisfy `<_ as chumsky::input::Input<'_>>::Span == SimpleSpan`
help: consider giving `lit` an explicit type, where the type for type parameter `I` is specified
   |
41 |         let lit: Select<{closure@/home/gh-estebank/.cargo/registry/src/index.crates.io-6f17d22bba15001f/chumsky-1.0.0-alpha.6/src/lib.rs:2782:13: 2782:28}, _, Expression<'_>, _> = select! {
   |                ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
```

Fix #123630.
2024-04-10 00:41:27 +00:00
..
generalize-subtyped-variables.rs [AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00
issue-30225.rs Move /src/test to /tests 2023-01-11 09:32:08 +00:00
issue-30225.stderr Show number in error message even for one error 2023-11-24 19:15:52 +01:00
issue-113283-alllocator-trait-eq.rs [AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00
or_else-multiple-type-params.rs Move /src/test to /tests 2023-01-11 09:32:08 +00:00
or_else-multiple-type-params.stderr Use `fn` ptr signature instead of `{closure@..}` in infer error 2024-04-10 00:41:27 +00:00
sort_by_key.rs Move /src/test to /tests 2023-01-11 09:32:08 +00:00
sort_by_key.stderr Show number in error message even for one error 2023-11-24 19:15:52 +01:00
unbounded-associated-type.rs Move /src/test to /tests 2023-01-11 09:32:08 +00:00
unbounded-associated-type.stderr Show number in error message even for one error 2023-11-24 19:15:52 +01:00
unbounded-type-param-in-fn-with-assoc-type.rs Move /src/test to /tests 2023-01-11 09:32:08 +00:00
unbounded-type-param-in-fn-with-assoc-type.stderr Show number in error message even for one error 2023-11-24 19:15:52 +01:00
unbounded-type-param-in-fn.rs Move /src/test to /tests 2023-01-11 09:32:08 +00:00
unbounded-type-param-in-fn.stderr Show number in error message even for one error 2023-11-24 19:15:52 +01:00