ring-span-lite
ring-span-lite copied to clipboard
martinmoene
ring-span lite - A C++yy-like ring_span type for C++98, C++11 and later in a single-file header-only library
Are ring-span's push/pop safe for unsynchronized consumer/producer scenarios? Does it even make sense to support such functionality given ring-span's domain (eg by using a policy) or does it make sense...
Hey, Your project looks promising. Can it work with shared memory? We would like to have a `ring buffer` between two different `processes` to share `images` and `metadata`
Hi Martin, I want to report that I am successfully using ring-span-lite on OSX 10.14 with this clang version: ``` clang version 6.0.1 (tags/RELEASE_601/final) Target: x86_64-apple-darwin18.0.0 Thread model: posix InstalledDir:...
Is this not "slow(ish)", when using the standard copying mechanisms: ```cpp std::copy(rs.cbegin(), rs.cend(), out_it) ``` ?? It'll call this unnecessary code on each iterator-dereference: https://github.com/martinmoene/ring-span-lite/blob/b8135cd85499a2d5482e048eb8fb6b354350d427/include/nonstd/ring_span.hpp#L968 which calls the slowish https://github.com/martinmoene/ring-span-lite/blob/b8135cd85499a2d5482e048eb8fb6b354350d427/include/nonstd/ring_span.hpp#L836...
Metadata
Owner
Metadata
ring-span lite - A C++yy-like ring_span type for C++98, C++11 and later in a single-file header-only library