View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0031163||Runner||Functions||Public||2019-07-11 10:32||2019-09-06 17:20|
|Reporter||Stewart Bishop||Assigned To||Russell Kay|
|Priority||Low||Severity||C - General||Reproducibility||100%|
|Target Version||2.2.4||Fixed in Version||2.2.4|
|Summary||0031163: Functions: We don't support writing buffer_f16|
|Description||Within the runner we have no support for these constants and converting from a float 32 to either of these is inefficient so we should remove these constants and update the documentation to match.|
|Steps To Reproduce||1) Create a project|
2) Create a buffer
3) Attempt to write a float 16 or 64 to the buffer
4) See that this has done nothing
5) Check the runner code and see there's no code to handle these
|Tags||No tags attached.|
|1.4 Found In|
|2.x Runtime Found In||18.104.22.1684|
|2.x Runtime Verified In||22.214.171.1241|
buffer_f64 definitely works, that's one of the most common types to use.
However, to note, it could be nice to rename buffer_u64 to buffer_s64 because it's being cast to signed 64-bit on read anyway.
Fixed in gitlab -
added the f16 in properly, so we do actually support it now.
f64 is already supported (it is a double).
no plans to change the u64 name just yet.