Jonas Nyrup

Thanks for opening this issue. I'm not sure this is natively possible in the way Fluent Assertions works. `Should()` works as a series of extension on types, e.g. https://github.com/fluentassertions/fluentassertions/blob/646dd3ba45146c537b0d56e242d180936e8e22d0/Src/FluentAssertions/AssertionExtensions.cs#L513-L516 which...

`Span` is a part of [.Net Standard 2.1](https://blogs.msdn.microsoft.com/dotnet/2018/11/05/announcing-net-standard-2-1/). Once that is released together with .net core 3.0, it should be possible to add extensions of `Should()` that convert `Span` into...

Yeah `Span` is *also* natively available in .Net Core 2.1. .Net Core 2.1 does not implement .Net Standard 2.1, but 2.0. .Net Core 3.0 is the first to implement .Net...

Just to recap. The following types * [`Span`](https://docs.microsoft.com/da-dk/dotnet/api/system.span-1?view=netcore-2.1) * [`ReadOnlySpan`](https://docs.microsoft.com/da-dk/dotnet/api/system.readonlyspan-1?view=netcore-2.1) * [`Memory`](https://docs.microsoft.com/da-dk/dotnet/api/system.memory-1?view=netcore-2.1) * [`ReadOnlyMemory`](https://docs.microsoft.com/da-dk/dotnet/api/system.readonlymemory-1?view=netcore-2.1) are available from from either * [.Net Core 2.1](https://blogs.msdn.microsoft.com/dotnet/2018/05/30/announcing-net-core-2-1/) (which has been release), or * [.Net...

Here's an example of what we can do without converting `[ReadOnly]Span` into `T[]` or `string`. It utilizes that `Span` is [implicitly convertible](https://source.dot.net/#System.Private.CoreLib/Span.cs,366) to `ReadOnlySpan` to avoid duplicating `ReadOnlySpanAssertions`. ```cs Span...

For the example of handling `Span` with `StringAssertions` I'm noticing that one cannot pass a `ReadOnlySpan` in as the expectation as all assertions take a `string`. ```cs Span a =...

Everyone who has shown interest in assertions on `Span`.

### testcase1 `RespectingRuntimeTypes` is necessary, as the compile time type of the expectation drives the comparison. ### testcase2 * both `BeEquivalentTo` resolves to `BeEquivalentTo(params object[] expectations)` `params object[]` uses runtime...

Here's an example of how to hit that line ```cs // Arrange var subject = new { DataSet = "foobar" }; var expected = new { DataSet = new DataSet()...

I'm wondering how chaining assertions should be handled, if the `IAsyncEnumerable` is not materialized. For most cases I assume materialization would be preferable to enumerating it multiple times?