AlgorithmsAreCool
AlgorithmsAreCool
Hmm, I'm gonna try to carve a little time to spike an implementation using [FASTER KV](https://github.com/microsoft/FASTER) for small to medium size responses. Notes for myself... - https://source.dot.net/#Microsoft.AspNetCore.ResponseCaching/ResponseCachingMiddleware.cs - (the aformentioned...
I'm guessing that the project isn't going to receive any updates for the foreseeable future. Which is a shame, but the library is pretty mature and is still usable
@johnds1974 No pain, no gain? 😉 It is very tricky to write complex queries but the performance was worth it for our use case
I've personally had great success with `RandomAccess`, but I'm curious about the perceived advantages of this addition? Performance? Consolidation?
I'll give it a shot in the next day or two
Hmm, ok. So, there is no API that defines the serializer's entry point. Each serializer must define their own ad-hoc method to accept `ISerialize` objects (and possible wrapper type). This...
> I was thinking of renaming everything to "proxy" but that has a long history of uses in .NET and I don't know if it would make sense to everyone....
Closing this issue for now since I don't have a concrete proposal
There are probably some hygiene features we can use such as more nullable annotations and use of the `scoped` keyword on stackallocated buffers.
Probably not a ton? It has to do with escape semantics of ref-like types such as Span since they can use stackallocated memory that is invalid if passed back to...