Are there any linked Issues or Pull Requests?
👉 Not yet, but there will be.
Brief description
There is no need for a separate data or name attribute on io_value_type b/c it inherits from key_value_type which already has a value and key attribute. This PR will remove those attributes and all the code pertaining to it, turning io_value_type into a specialisation of key_value_type whose only difference is that it contains procedure pointers for doing IO.
The existing interfaces for key_value_type may have to be extended to handle 32-bit reals.
Further details of the issue.
A previous issue (#183) to refactor io_value_type so that its attributes were private has been closed. The attributes of key_value_type are purposefully public to make the code simpler.
Are there any linked Issues or Pull Requests?
👉 Not yet, but there will be.
Brief description
There is no need for a separate
dataornameattribute onio_value_typeb/c it inherits fromkey_value_typewhich already has avalueandkeyattribute. This PR will remove those attributes and all the code pertaining to it, turningio_value_typeinto a specialisation ofkey_value_typewhose only difference is that it contains procedure pointers for doing IO.The existing interfaces for
key_value_typemay have to be extended to handle 32-bit reals.Further details of the issue.
A previous issue (#183) to refactor
io_value_typeso that its attributes were private has been closed. The attributes ofkey_value_typeare purposefully public to make the code simpler.