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
Zig tuples (side requirement... we can fudge this if we need to)
With wasm supporting multiple returns and Zig doing tuples, we can actually return "complex" data without bitcast kludging. It's still not as nice as (named field) structs, but it's much better than the current representation.
Note — this depends on upstream features:
With wasm supporting multiple returns and Zig doing tuples, we can actually return "complex" data without bitcast kludging. It's still not as nice as (named field) structs, but it's much better than the current representation.
tuple { [*]T, usize }
tuple { [*]T, width: usize, height: usize }
tuple { [*]u8, usize, length: u8 }
The text was updated successfully, but these errors were encountered: