Steven Giesel
Steven Giesel
Just to clarify: I am interested in backporting this onto older .net versions, but the benefit might be neglectable (in comparison to `System.Text.StringBuilder`).
I tried to support `netstandard2.0` - most fixes are done via the `System.Memory` package that backports `System.Span` and friends. Some other fixes are done via `#ifdef !NETSTANDARD2_0`. If it would...
The same seems to apply to `Any`: `Tags.Any(t => t == Tag)` which results in somewhat the same SQL code.
Can you elaborate what specific behavior / API you are missing? `new ValueStringBuilder(stackalloc char[256])` is working in this library, just like in the linked article.
Interesting - that we could do. I am not sure if we have this as a parameter or an explicit static version like: ```csharp using var builder = ValueStringBuilder.CreateStackOnlyNonGrowing(stackalloc char[512]);...
On second thought, it will not be a `static` method, but a new type with maybe limited API. That makes it easier to understand.
The flag has the issue, that it is non-obvious what happens in edge-cases or functions that might not exist. I do think its own type, would do more justification here....
True - but that would incur allocations.
I think that depends a bit on the struct layout and stuff, but you might be right - I would need to do more research
That is an interesting case and for sure a bug! Your first given option should be what is happening. That is what the user configured. I understand the test-setup is...