Dan Johnson

I found this while running the 2021 edition migration over the Fuchsia codebase, you can see the full example pre-minimization in https://fuchsia-review.googlesource.com/c/fuchsia/+/684586/1/src/settings/service/src/tests/setting_handler_tests.rs if that's interesting.

https://github.com/dtolnay/async-trait/pull/203 seems to fix it for `_` patterns as arguments, but not patterns with underscores nested inside them: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=2d998a28f5b49520167ef0868f0beab5 It drops the argument early if edition is set to 2021,...

Instead of `{List of String}` I'd be much happier to see the typing syntax used for python: https://www.python.org/dev/peps/pep-0484/ . So that's be written as `{List[str]}` (assuming you still need the...

reported upstream in https://github.com/kvark/blade/issues/104

> What about `next_or_never` or similar, after [`Future::now_or_never`](https://docs.rs/futures/0.3.5/futures/future/trait.FutureExt.html#method.now_or_never)? That seems to be a close analog to `Receiver::try_next`'s behavior. It is very similar, but it isn't really `_or_never` since it doesn't...

Side note: I probably could have gotten this to work with a dylib instead of a cdylib, but I was really struggling to get it to work at all and...

> "Regular" dynamic libraries aren't affected because their path is essentially hardcoded Basically yes, it uses the system search path which is not relative to `$ORIGIN`. Only "bundled" libraries would...

the parent expression is a call here, but its span includes one layer of parens: ``` error: par_expr.span --> tests/ui/legacy_numeric_constants.rs:125:20 | LL | assert_eq!(0, -(i32::max_value())); | ^^^^^^^^^^^^^^^^^^ ``` so yeah,...

@rustbot claim Working on a fix which replaces the whole `par_expr`.

If the motivation for putting it in std is just for FFI, could the std one just be a struct with pub fields and no other API, and then have...