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
A void_array (a DataArray<void*> instance) would be useful for the case were you want to generically stride though and access the bytes for any array w/o type checking.
The void_array will still have access to the full data type spec, so the parts of the DataArray inteface related to set, to_json, etc helpers could still work fine, but we need to look if it has implications on plumbing of the template use.
The text was updated successfully, but these errors were encountered:
We can effectively access and iterate over the data directly from a node via element_ptr().
The main benefit of this comes in the a case where you have a leaf Node that you don't want to access with a specific bw style type, but you have some data values you want to set:
void_array arr = n.value();
arr.set(...) // pass in ptrs to btw style types, any other data array, etc
That said, the bracket operator overloads don't really make sense in this context. We could try some sort of magic that would mirror Node::Value, but that seems extreme.
As such "void_array" doesn't really adhere to the DataArray interface -- so we should think of a different way to provide what is needed.
A void_array (a DataArray<void*> instance) would be useful for the case were you want to generically stride though and access the bytes for any array w/o type checking.
The void_array will still have access to the full data type spec, so the parts of the DataArray inteface related to set, to_json, etc helpers could still work fine, but we need to look if it has implications on plumbing of the template use.
The text was updated successfully, but these errors were encountered: