Marijn Suijten

Cross-posting from https://github.com/ash-rs/ash/pull/969#issuecomment-2514806681: I don't think this issue is actionable if we don't want a breaking release any time such a struct starts being referenced in a new `structextends`. This...

I doubt they would want to commit to that, but we could try. I have no reason to pursue this (kept it out of the `0.39` milestone) as it's very...

Our `no_std` build complains: ``` error[E0412]: cannot find type `Vec` in this scope --> ash/src/extensions/khr/pipeline_binary.rs:66:19 | 66 | ) -> VkResult { | ^^^ not found in this scope |...

There's a plan to rewrite most of the readme anyway, lots of it has gotten stale or is referencing old external links, and it's generally too verbose in demonstrating minute...

It seems useful to me to have these functions available - with the right `# Safety` context - to hopefully prevent users from implementing it themselves without being aware of...

@fu5ha Good point on the `offset` and `len`! Not sure if we should: 1. Merge this PR as a stop-gap solution; 2. With or without `MaybeUninit`; 3. With or without...

@fu5ha Sure! This PR only took a few minutes to rig up, I'm fine with closing it and migrating the whole public mapping API to `presser` as a whole. We...

Sounds good! CC @manon-traverse @Jasper-Bekkers :)

> I think we should always provide a mapping api in order to not break this crate Yeah, it would always go through `presser` in that case, and we should...

@djkoloski That is effectively - exactly - what I wrote two posts above yours :wink:. This is planned, I just have had too much on my plate to look into...