Anton Zhilin
Anton Zhilin
Hi! IMO, it's acceptable to leave NonFifo Queue name as-is. It follows from their name that they generally aim for queue (FIFO) semantics, but sometimes shuffle the elements in a...
> is that an artifact of the internal->external github synchronization you guys maintain? Yes, some work is still needed to complete the migration from the internal repo.
Both Readme and the documentation landing page could really be more informative and helpful. [This page](https://userver.tech/d6/d2f/md_en_index.html), takes a couple of hops to get to.
You would usually want to handle values inside the loop and the sentinel outside the loop: ``` auto gen = make_generator(); while (co_await gen.next()) { use(gen.value()); } use(gen.sentinel()); ``` So...
We could have a separate second task queue for `Yield`-ed tasks. Low-priority work like background cache updates can also go there. This work can go independently from investigating a non-thread-migrating...
Let's continue here: #384
Will try to merge lock-free `WaitList` some time soon, after that the path is clear
This can be implemented without patching rapidjson itself. `formats::json::FromString` can use a wrapper class/struct around `impl::Value` with rapidjson visitation API that keeps track of the depth and forwards to `impl::Value`'s...
We should actually use just Boost.Stacktrace instead of using our copy in `third_party/boost_stacktrace`.
Fixed in https://github.com/userver-framework/userver/commit/68574f5b83f560ab802bef79c6ae5795493efc1d