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
vector vs SmallVector vs span: There should be a single way to represent a (dynamic) array of elements. The span is an ideal option as it represents an interface rather than a class, but even std::vector or SmallVector are okay if they are used consistently.
The text was updated successfully, but these errors were encountered:
dgomezTT
changed the title
Improve consistency in how we store dynamic array of elements
Improve consistency in how we pass around dynamic array of elements
Feb 4, 2025
Basically, what we want to unify to Span instead of SmallVector in op invoke methods.
Please keep in mind, span does not maintain ownership over data. But from the interface standpoint it is convenient to accept span as it allows whatever input, whether its array, vector, smallvector or any other compatible container.
There are cases where a fixed size array is used. Such cases are out of scope of this effort
vector vs SmallVector vs span: There should be a single way to represent a (dynamic) array of elements. The span is an ideal option as it represents an interface rather than a class, but even std::vector or SmallVector are okay if they are used consistently.
The text was updated successfully, but these errors were encountered: