readerwriterqueue VS lqml

I have looked at the commonly recommended - https://github.com/cameron314/readerwriterqueue - https://github.com/rigtorp/MPMCQueue

The PREEMPT error looks like its a C module but I cannot tell from he little snippet of the log - you may do better to move the *arr and Synchthing into Docker containers to keep the OS cleaner.

For audio DSP in a Qt app I have good success with using a lock-free queue (e.g. https://github.com/cameron314/readerwriterqueue) to communicate from / to the UI threads. Code more-or-less looks like

    connect(model, &ModelObject::somethingChanged, [=] {

We recently removed readerwriterqueue from our project due to issues and replaced with simple locking queue (and got better performance in the result). Your code looks interesting, but we can't use it due to C++17 usage.

Was wondering how practical using lqml for developing Android apps would be.

screenshot / repo / official meshtastic web site

There is lqml, which is cross-platform, including iOS.

Check out https://gitlab.com/eql/lqml and other repositories in this group.

The advantage of LQML is that you can develop your app on the desktop first (as I did with the cl-repl app), mostly without restarting anything, because QML can be reloaded at runtime. A good example to learn how this works would be this one: qml-auto-reload

Notably - 1. https://github.com/lispnik/iup/ 2. https://gitlab.com/eql/lqml 3. https://github.com/bohonghuang/cl-gtk4

In this example, there is an example call to Objective-C, which in turn is callable from Lisp.