Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Drop order of async fn arguments doesn't exactly match the equivalent regular fn. #60236
While #59823 resolved
This is visible in this playground example which compares the drop order of four functions with and without
The only argument I can come up with in favor of this drop order is basically:
You might make a case that, because people sometimes have to manually desugar into a fn that returns an async block for various reasons, having a simple transformation is important.
But I think this whole case sounds a bit weak to me -- in contrast, matching fn and async fn as closely as possible feels like what would people would expect
Of course I also think that the drop order between fn parameters, particularly when intermingled with complex patterns, is highly unlikely to matter, but who's to say what people ultimately rely on.
Still, this implies that most of the time, people can desugar any which way to use an