Stuart Lang

Ok, so I went to add the target framework change I mentioned above (bullet point 2), and it's actually already a thing. There is a `Build` overload that takes a...

> Doing this will _probably_ end up doing #874 too (or at least make it easier to do). easier to do for sure. To go back to our conversation, for...

Thanks for the PR @nelsonroliveira My understanding is that this was by design, however in my opinion it feels wrong. We can change this default, and it would be a...

This PR should solve this, I am suggesting we change the default for v5 with the ability to toggle it back via config: https://github.com/shouldly/shouldly/pull/1094

If we are to support assertion scopes, it should work without the additional `ShouldWithScope` methods, so the builtin assertion throw helpers would need to be aware of scopes.

Yes, the solution would likely need to utilize an `AsyncLocal` as an ambient context, and anywhere we would throw an exception we'd collect them there instead.

I've ran a before and after below. There's still at least one significant v4 perf improvement on the way, but I expect EfficientDynamoDb will always be significantly faster, even if...

@bill-poole sure. @normj and the AWS .NET team would be interested I'm sure. Looking at the [v4 preview announcement here](https://aws.amazon.com/blogs/developer/preview-1-of-aws-sdk-for-net-v4/#:~:text=upgrading%20to%20V4.-,Performance,-With%20the%20changes), it's clear that v4 represent a performance boost, and not...

I finally got around to benchmarking this again, and wrangling with BenchmarkDotNet to handling multiple package versions. It confirms what we already suspected - AWSSDK V4 is a noticeable improvement,...

Thanks for taking the time to explain the scenarios @jaredpar, I see this being really useful to the compiler team. I've been keeping an eye on this space, my scenario...