…n blocks
`ParameterExtensions`, `ReturnsThrowsAsyncExtensions` and `CallbacksExtensions` were the last public files that still used classic `this` extension methods, so the source and the API snapshots mixed two styles.
- Not breaking: the lowered metadata signatures (names, generic parameter order and constraints, parameter types, defaults, `[CallerArgumentExpression]`) are identical on all target frameworks, and test assemblies compiled against main pass against the new library, including already generated mocks that call `CallbacksExtensions.Register<T>`.
- Explicit type arguments in extension form (`setup.ReturnsAsync<int>(5)`) still compile; they bind to the block's type parameters.
- The generated `ReturnsThrowsAsyncExtensions2` for higher arities stays classic.
ParameterExtensions,ReturnsThrowsAsyncExtensionsandCallbacksExtensionswere the last public files that still used classicthisextension methods, so the source and the API snapshots mixed two styles.[CallerArgumentExpression]) are identical on all target frameworks, and test assemblies compiled against main pass against the new library, including already generated mocks that callCallbacksExtensions.Register<T>.setup.ReturnsAsync<int>(5)) still compile; they bind to the block's type parameters.ReturnsThrowsAsyncExtensions2for higher arities stays classic.