Repository navigation
Option for platform without threads, mutexes #704
Description
Hi @victimsnino ,
it's been a while since bothering you with further requests. So, i am back 😉
Recently, i started developing on a raspberry pi pico 2 and i would love to use rpp for this. Unfortunately, this platform is missing posix threads, as well as mutexes, etc. Can you imagine a version of this lib without those things?
Besides that, it seems possible, that rpp is usable on that platform.
Regards 😀
Reacted by Aleksey Loginov
Activity
AlexInLog commentedon Feb 11, 2025
Hey @mincequi ! Yeah, you are welcome =)
Would it be enough just to have limited functionality just by splitting headers and not providing operators/functionality relying on threads/mutexes? For example, just provide observable/observer/filter/map and etc? Or do you expect something more? I mean... if yes, then technically it is possible to use it "as is"?
mincequi commentedon Feb 11, 2025
Hey @victimsnino,
of course splitting functionality is perfectly fine for me. So, only "immediate execution" operators would work and is ok for me :)
One could later check, if scheduling is somehow possible on that platform.
edit: i already tried to only include the (few) things i need, but utils.hpp gets included which includes the mutex header.
AlexInLog commentedon Mar 11, 2025
Hey @mincequi , it was a short break for me from RPP, now i'm ready to back to development. Does this issue still relevant to you?
mincequi commentedon Mar 14, 2025
Hi @victimsnino ,
currently, i have a custom implementation to emit events from an object and i do not have an urgent need for an RPP port.
There is also an arduino impl for Rx: https://github.com/luisllamasbinaburo/Arduino-ReactiveArduino
Maybe this can also help.
One could just keep that in mind, if you ever plan to port this to a non-threaded platform.
daixtrose commentedon Oct 30, 2026
How about building on coroutines?
AlexInLog commentedon Oct 30, 2026
Hey! I've thought about it, but actually it is nearly zero profit to do it. For now RPP is fully push-based and no any places to "wait" something. So, current "on_next" executed in place. Making coroutine would just break stack and prove extra overhead.
If you have some other opinion, I would be glad to see it