Likely no difference. Tuple is obsolete anyway - it does not have nice syntax, can't have named values, etc. If you'd like to avoid allocations in a hot but asynchronous path you'll need to execute this together with other code and use ValueTask PoolingAsyncValueTaskMethodBuilder

PoolingAsyncValueTaskMethodBuilderをつけると、asyncでout/ref書いたのがコンパイル通っちゃう（が、正常に動かない）。これはコンパイラのバグでいいですかねー？

🤩Comments like this makes us love the fact that #runtime #dotnet repo is open on GitHub even more! So much knowledge in there! Also, please notice a fancy usage of #PoolingAsyncValueTaskMethodBuilder 😎 #async #asyncawait #asyncexpert #net5 #net6 github.com/dotnet/runtime/bl…