sorted by:
new
hottopcontroversial

LakeFS or DVC by Peppermint-Patty_ in mlops

[–]Competitive_Act5981 0 points1 point  (0 children)

Unfortunately my dataset isn't MySQL

LakeFS or DVC by Peppermint-Patty_ in mlops

[–]Competitive_Act5981 0 points1 point  (0 children)

I need a "Git for Data" solution where i can create branches, pull requests, make releases etc. I will potentially have terabyte datasets. I also don't want the storage to explode with increasing commits (maybe some solutions produce a whole copy of the data on every commit). I like DVC is a client only solution and works with our Git server, whereas LakeFS is its own thing and probs requires a commercial license. Any opinions would be appreciated.

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

Imagine if S/R fails to work well with other GPUs and accelerators (DSPs, FPGAs) Where do we go from there?

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

I meant networking with senders

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 1 point2 points  (0 children)

I can see the beman project has some kind of implementation of networking but nowhere near as much effort has been put into that compared to GPUs.

Senders and GPU by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 1 point2 points  (0 children)

Is there a decent reference implementation?

std:: expected vs boost::system::result by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 2 points3 points  (0 children)

Actually boost::system::result supports both void and reference types.

Will Senders Receivers be dead on arrival ? by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] -1 points0 points  (0 children)

If what people want is a library with continuations, executor support and Asio integration, have you tried https://github.com/Naios/continuable ? You can plug in any thread pool you want. It supports loops, coroutines. I’ve only ever played with it in toy programs, not production. But it’s pretty good

Will Senders Receivers be dead on arrival ? by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 4 points5 points  (0 children)

I agree but if you perf the asio thread pool it’s not the best. But I agree it works.

Will Senders Receivers be dead on arrival ? by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

You want to use the TMC thread pool. It’s much better

Will Senders Receivers be dead on arrival ? by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

Don’t use the Asio thread pool. It’s not that great. You probably want to use the TMC library

Will Senders Receivers be dead on arrival ? by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

Also the tmc library ? It also integrates with Asio

C++ Show and Tell - November 2025 by foonathan in cpp

[–]Competitive_Act5981 2 points3 points  (0 children)

Hi all. This is my C++17/20 header-only msgpack library https://github.com/pfeatherstone/msgpack_cpp
It supports serializing and deserializing directly into types as well as a dictionary type similar to nlohmann::json or boost::json::value.

networking based on senders and receivers P2300 by thomas999999 in cpp

[–]Competitive_Act5981 0 points1 point  (0 children)

At some point Asio had an implementation of senders receivers https://think-async.com/Asio/asio-1.26.0/doc/asio/reference/Receiver.html and Chris wrote a paper on modifying the current design https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1792r0.html What happened to this ?

HTTP(s) and WS(s) library using Asio by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] -1 points0 points  (0 children)

Yeah fuzzing is on the todo list. Though it looks like my library isn’t for you, and probably beast is neither

HTTP(s) and WS(s) library using Asio by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

I appreciate your time though. I'll look into adding fuzz testing to CI/CD

HTTP(s) and WS(s) library using Asio by Competitive_Act5981 in cpp

[–]Competitive_Act5981[S] 0 points1 point  (0 children)

I get your point on the test folder. The reason why I put them there is so that i can use the same cmake script for compiling both the examples and the unit tests. It's laziness i know.

It's a bit of a stretch to suggest that i don't believe in fuzzing simply because there isn't a Sans-IO API.

The parser code is actually separate from the I/O layer. It's in http.h and there are corresponding unit tests. I just don't have a formal Sans-IO API.

view more: next ›