Jira (PUP-3133) Decide on the specification of Integer/Float runtime types

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on an issue   Re: Decide on the specification of Integer/Float runtime types And to complete - any serialization format, even if specified to support unlimited sized integers sooner or later needs a concrete implementation that is limited by the language / platform serialization/deserialization takes place on. _javascript_ numbers are max 2^53 (because they are floating point), most json implementations are 2^63 (i.e. unsigned long). Add Comment   Puppet / PUP-3133 Decide on the specification of Integer/Float runtime types Currently, the Integer runtime type is specified the way integer values work in Ruby - i.e. there is never an overflow as the implementation shifts to use the required number of bits (e.g. a BigInteger is used if the value is bigger than unsigned 64 bit int). The same promotion to BigDecimal takes place for floats. The problem with this is the serializ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.