Alex Norman

BTW.. the [c docs](https://ossia.io/libossia/html/group___c_proto.html#ga37fa6608347f26863ee91d1d91c2a8c0) claim that `ossia_protocol_multiplex_expose_to` is MT safe.. it pushes to a vector which is also accessed from other threads.. the docs from std::vector AFAIK don't indicate that...

> indeed, I think that we had discussed that at some point with @bltzr ? > should not be hard to fix, I wonder if it would break some workflow...

here is what bindgen says about c++ https://rust-lang.github.io/rust-bindgen/cpp.html You can also call c++ directly from rust, but providing a wrapper `-sys` library is the common approach for rust bindings to...

I've never experienced a duplex stream with buffer sizes that are different for input vs output. It is very common to have differing channel counts for inputs vs outputs.. in...

> Thanks. What about the remaining aspects: > > * mixed types (`i32`, `f32` , …) > > * mixed endianness > > * channel interleaving > > * number...

I'm wanting to interface with 25LP064 QSPI flash memory and so I'm hoping my efforts can help this HAL. I'm wondering if you all have any advice for the API...

> In the example in that PR there's an instruction with no address and no data phases ([line 80](https://github.com/stm32-rs/stm32h7xx-hal/pull/230/files#diff-37e1cf6c7c3da03fb936b858738b81830c681cced7575695592991fb5186d7ceR80)), as well as an instruction with both address and data phases...

Been a while, figured I'd ping here again.. @btrepp any thoughts?

> Hi Mate. Hey, thanks for taking a look! > > I've had a look. Overall it's okay, it's a bit hard to grok with the re-org plus type changes....

> > So to simplify, > > 1. Happy to take any types from the shared crate > > 2. Lets take simplifications in their own PRs, so we can...