rust/compiler/rustc_trait_selection/src
Matthias Krüger 457087ed29
Rollup merge of #131549 - compiler-errors:try-in-sync, r=spastorino
Add a note for `?` on a `impl Future<Output = Result<..>>` in sync function

It's confusing to `?` a future of a result in a sync function. We have a suggestion to `.await` it if we're in an async function, but not a sync function. Note that this is the case for sync functions, at least.

Let's be a bit more vague about a fix, since it's somewhat context dependent. For example, you could block on it, or you could make your function asynchronous. 🤷
2024-10-22 15:28:41 +02:00
..
error_reporting Rollup merge of #131549 - compiler-errors:try-in-sync, r=spastorino 2024-10-22 15:28:41 +02:00
errors Reformat using the new identifier sorting from rustfmt 2024-09-22 19:11:29 -04:00
solve Rollup merge of #131825 - lcnr:probe-no-more-leak-2, r=compiler-errors 2024-10-17 20:47:31 +02:00
traits Auto merge of #131840 - compiler-errors:impossible-maybe, r=lcnr 2024-10-21 22:58:44 +00:00
errors.rs Reformat using the new identifier sorting from rustfmt 2024-09-22 19:11:29 -04:00
infer.rs move defining_opaque_types out of Canonical 2024-10-17 10:22:52 +02:00
lib.rs Stabilize the map/value methods on ControlFlow 2024-09-25 19:00:17 -07:00
regions.rs Reformat using the new identifier sorting from rustfmt 2024-09-22 19:11:29 -04:00
solve.rs impossible obligations check fast path 2024-10-10 06:09:50 -04:00