The upcoming release of onnxruntime 1.16 breaks our build because they forbid direct assignment from already encoded uint16_t to their Float16_t. They do provide access to the uint16_t val member, but this was named value in previous versions, so it can't be used for direct assignment in a portable way.
The upcoming release of onnxruntime 1.16 breaks our build because they forbid direct assignment from already encoded
uint16_tto theirFloat16_t. They do provide access to theuint16_t valmember, but this was namedvaluein previous versions, so it can't be used for direct assignment in a portable way.