Closed MordechaiHadad closed 1 year ago
Is there any particular reason write() doesn't allow the passing of u64?
The fundamental reason is that u64
isn't support by Excel.
All Excel numbers are stored in f64
so u64
can't be supported. All the other integer types will convert Into
f64
so they are handled.
Generally Excel users are constrained to storing u64
style values as strings.
Oh fair enough, thank you for the quick response.
I've been thinking recently about supporting u64/i64 within the limits of Excel's support. So basically u64/i64 would be accepted by write()
but stored as f64 like in Excel. This would be a lossy conversion outside +/- 999,999,999,999,999 but for most users that would be okay.
Would that work for the use case you enquired about?
Yeah that sounds like a good solution, but personally for me f64 suffices at this point lol.
Thanks for the feedback. I'll put that in the next release.
This support is on main now and will be in the next release.
Question
Is there any particular reason write() doesn't allow the passing of u64?