You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing out from an encase Buffer via into_inner/as_ref getting e.g. a Vec<u8>, that inner structure has unaligned length (there might be padding missing at the end of it).
This makes it impossible to append anything to a GPU-side buffer after having written to it with encase-data once, because how will one know the next properly aligned offset?
Would be great to just have a get_(next_)offset function along the already existing set_offset on encase’s types.
The text was updated successfully, but these errors were encountered:
For the dynamic buffer types you can keep writing, they have an internal offset that keeps increasing. .write(value) also returns the offset where the value was written to.
When writing out from an encase Buffer via
into_inner/as_ref
getting e.g. aVec<u8>
, that inner structure has unaligned length (there might be padding missing at the end of it).This makes it impossible to append anything to a GPU-side buffer after having written to it with encase-data once, because how will one know the next properly aligned offset?
Would be great to just have a
get_(next_)offset
function along the already existingset_offset
on encase’s types.The text was updated successfully, but these errors were encountered: