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
{{ message }}
This repository was archived by the owner on Jun 12, 2024. It is now read-only.
char arrays have always been ambiguous since they may contain either numerical values or strings. Currently these are always read as numerical values, and the clients are responsible for recasting to a string.
It would be great to declare the intended high-level type of ambiguous low-level types such as char arrays. This could be part of the info contained in an "extended header" along with other new features. Then the client could automatically cast char arrays containing text to a string type (similar to casting numeric arrays to numpy arrays #29).
The text was updated successfully, but these errors were encountered:
char arrays have always been ambiguous since they may contain either numerical values or strings. Currently these are always read as numerical values, and the clients are responsible for recasting to a string.
It would be great to declare the intended high-level type of ambiguous low-level types such as char arrays. This could be part of the info contained in an "extended header" along with other new features. Then the client could automatically cast char arrays containing text to a string type (similar to casting numeric arrays to numpy arrays #29).
The text was updated successfully, but these errors were encountered: