4 ms·

Also why num/num32 for Integer types, and no floating point type

• hedayet 8mo ago
  [author here] Very good questions; I definitely would like to revisit num32 very shortly. I'd say the initial rational of having num32 is not coherent right now, but I'll have to verify removing the support. we have floating point type(It was missing from the type list in readme. I have just updated that seeing this comment. thank you!)
  • teiferer 8mo ago
    Well, clarity would be achieved with a name like u64. Is num signed? What's the range? Is it integers or floating point? All these things are hidden. With u64 there would be no questions open. (Well a few maybe, like overflow behavior, but can't have it all..)
  • rurban 8mo ago
    There cannot be any num32. num is a number, which can be fixed size integers, floating point numbers (of fixed size or not) or bigints. Some also add decimals num32 being i32 or f32 makes no sense
• hedayet 8mo ago
  now we have only int64 for integer types and float64 for floating point types. Thanks everyone for your thoughtful feedback!
  • rkeene2 8mo ago
    Neat !