Guillaume Fraux

I agree that this could be built against a separate branch as multiple smaller PR, I've created a `nightly` branch for this! > Decide the code organization. I'm leaning towards...

Also, before spending too much time working on tests & setup for this single length optimization, it would be good to have the code in a state able to run...

Yes, this is a known limitation of this crate. I think it would be worthwhile to have a single pointer for each member of the struct, plus two `usize` (len...

By `RawVec` you mean using the one in `alloc`, right? It [looks like](https://github.com/rust-lang/rust/blob/1557fb031b272b4c5bfcc7de5df7eddc7b36a584/src/liballoc/raw_vec.rs) it is unstable with no path for stabilization, meaning using this would lock soa-derive on nightly. I...

The advantage of soa_derive is on the API side: being able to consider a XXXVec exactly like a Vec, and use `vec.push(e: XXX)` and all other Vec methods directly. One...

I agree that preventing desynchronization is good, as long as we can still provide access to individual slices with or without `soa_zip!`. > Right now, the tests rely on having...

@iMplode-nZ moving the discussion on single length here. --- Hm for the single length thing perhaps just make the storage generic and use a HList? _Originally posted by @iMplode-nZ in...

Except that in your example, since `SOAStorage` contains a Vec, any `SOAStorage` containing more than one field will contain the length multiple time. We could have a `FirstFieldSoaStorage` and `OtherFieldsSoaStorage`...

Hey @copying! Thanks for working on this. Unfortunately, I don't have a lot of time to spend on this crate these days. I'll try to give a look at your...

I dit not know about this feature, it seems nice! I'm not sure if changing the doc to this new use of attributes can be done without bumping MSRV though.