Jonas Nyrup

FYI, [ImageSharp 2.0.0](https://github.com/SixLabors/ImageSharp/releases/tag/v2.0.0) has just been released.

> FYI I removed `execabs` in #1093 - does this solve the problem for you? I just tried out 6.6.1 and it solved the problem for me 🎉

@94sedighi Please wait until the API is approved before opening a PR.

Alright, then I'll approve the API addition too. ```cs public class BooleanAssertions { public AndConstraint Imply(bool expected, string because = "", params object[] becauseArgs) } ```

> Is there a way to extract the _expectation_ variable name? Not currently. We would like to look into using `[CallerArgumentExpression]` for this purpose. This is listed in #1677.

Using approach 2 is also problematic Writing this idiomatic FA code ```cs subject.Should().Imply(implicator, "because we want to test the {0}", "failure"); ``` fails with this unexpected message ``` Expected subject...

I think we should stick with the approved API, i.e. not using `[CallerArgumentExpression]`. Other APIs that might also benefit from having the name of the expectation, like `ReferenceTypeAssertions.BeSameAs`, would face...

Wow, I have never thought about nested `IAsyncEnumerable`s and performing equivalency assertions on them 😮 I find it hard to imagine how `BeEquivalentTo` would handle async properties without blocking 🤔

@zachsaw-lmg If we have a _bug_, please open a separate issue for that.

#1575 improved this by excluding internal members. before (1280 lines) ``` Expected col to be null or empty, but found {HtmlAgilityPack.HtmlNode { _attributes = _childnodes = _endnode = _innerhtml =...