If you belong to the chosen few who use #RxCpp here is some advice for free: Don’t use rxcpp::operators::sample_with_time. Or don’t use ThreadSanitizers, but that is bad advice. Repro and bug report take some time. Please stay patient.

Abusing #rxcpp to the point it kills VS2019 C++ compiler (cc: @kirkshoop) developercommunity.visualstudio.com/content/proble…

I ended up watching a talk from #CppCon 2016: @kirkshoop about Async algorithms for values distributed in time youtu.be/FcQURwM806o #rxcpp

Reactive programming: "Learning it is hard, even harder by the lack of good material" gist.github.com/staltz/868e7e9… #rxcpp #cpp

Giovanni, our intern who is working on observable ML models using #rxcpp, wrote a great blog post about the first part of the project, blog.detoni.me/2019/04/04/Obs…

How many here care about msvc 2013 support in #rxcpp? upgrading to #catch2 as part of the pr to add a no-exceptions mode to #rxcpp has broken the CI builds on 2013. I would like to drop the VS 2013 builds on #appveyor.

@kirkshoop feeling like a newbie with #RxCpp: With operator window do we need as_blocking() in the inner subscription or is there some magic going on?

#pushmi now has Many and FlowMany, which means that the #rxcpp operators can be built in pushmi! array<int, 5> v{0, 1, 2, 3, 4}; op::from(v) | op::submit([](int){}); op::flow_from(v) | op::for_each([](int){}); godbolt.org/g/xM7oKy

For those that want #rxcpp in std:: the first step has begun. The root of the concept hierarchy is being defined by future and executor proposals.

kirk shoop @kirkshoop

7 years ago

For those that want #rxcpp in std:: the first step has begun. The root of the concept hierarchy is being defined by future and executor proposals.

1 2 9 0 0

@FlohOfWoe It is the foundation of algorithm libraries like #range-v3 and #rxcpp

@Norman1604 Long live #rxcpp! I am actively talking with multiple people using rxcpp. My time has been limited by some family obligations over the past year, but I do support rxcpp. There are others that chime in on questions as well and I love contributions of all kinds!

It seems to me #rxcpp is dead, can you confirm @kirkshoop? We want to use it in a productive environment, but are really hesitant to use a library that's not actively developed anymore #react #reactive #cpp

@meetingcpp Almost never use bare threads since using #rxcpp

@Code_Analysis You may want to add #rxcpp and @noesisengine to your list :)

@CppCon early in atanasoff watching twitter #cplusplus #rxcpp

Got on twitter to set up this example. Guess I'm gonna stay a while #myfirstTweet #imgui #cpp #RxCpp #twitter #live #analytics

@ericniebler @kirkshoop @DrSolaAina The main reason I am using #rxcpp to do async things... thx to @kirkshoop

C++Now 2017: Kirk Shoop "No raw std::thread! - Live Tweet Analysis in C++" #cpp #rxcpp #reactive #rx #concurrency youtube.com/watch?v=1-8gxw…

@kirkshoop Are there #rxcpp wrappers available for github.com/Microsoft/cppr… (or for the pplx::task used therein)?

@mattgodbolt @foonathan @meetingcpp Me too - which is why #rxcpp supports . and | to chain alg. Trade off is to edit class to add a new . alg and alg/class have circular dep.