Hadrien G.

If you have a version of clang around, then `acts%clang@14` should work, the problem is automating it so that it keeps working with new dpcpp and upstream clang releases... I...

From a quick discussion with @krasznaa, who's the author of the vecmem and ACTS SYCL support code, it should be easier to get vecmem to build in SYCL mode than...

@krasznaa It seems Spack picked up your ROCm compiler. You probably don't want to use that for building hipsycl (and the entire stack below it). This is not a big...

It would ensure safety in the presence of misaligned buffers (since [u8] itself has no such requirements), but using uninitialized memory as returned by e.g. UEFI's memory allocator would still...

Possible clue for current CI failures, but does not explain the one you observed previously where stripping out all test code wouldn't resolve the problem: https://github.com/rust-osdev/uefi-rs/pull/114#issuecomment-573542870 .

There is now [another Rust REPL project](https://github.com/google/evcxr) that somehow managed to work on more recent compiler releases and support Jupyter. Probably it could be used for inspiration or joined forces...

In my application, I maintain an AtomicBool that indicates if the audio thread is alive in the shared state between the audio threads and other application threads: ```rust // Check...

Oh, wait, I think I got it. One headliner feature of jack2, which I also use, is that it supports multiple audio processing threads. What I did not realize is...

Note that if there are multiple audio threads and they can work concurrently, some aspects of the `jack-rs` API may need to change towards multi-thread-safety. For example, `NotificationHandler` and `ProcessHandler`...

> using Arc is not an option because its spinlocks are not thread safe Can you clarify what you mean by that ? > If I understand https://github.com/jackaudio/jackaudio.github.com/wiki/WalkThrough_User_ClientThreads correctly, there...