Figure out what to do about operations on int values outside the comfortable JS range

[rakudrama]

Issue #636 was that parsing hex literals resulted in incorrect values.
However, the numbers are still represented by JavaScript doubles, leading to various incorrect values.
Arithmetic operations are mostly correct up until rounding at 53 bits.
Bitwise operations are truncated to 32 bits.

[jmesserly]

Here's a strawman:

* Make ints 32 bits in Frog.

• overflow checks in checked mode (throw error on overflow)
• omit checks in unchecked mode (for best performance)

Provide a "long" type implemented in Dart that works for arbitrary length arithmetic.

---

Removed Type-Defect label.
Added Type-Enhancement label.

[dgrove]

Issue #1534 has been merged into this issue.

[anders-sandholm]

Removed Area-Frog label.
Added Area-Dart2JS, FromAreaFrog labels.

[kasperl]

Removed FromAreaFrog label.
Changed the title to: "Figure out what to do about operations on int values outside the comfortable JS range".

[kasperl]

Added this to the Later milestone.

[kasperl]

Removed this from the Later milestone.

[kasperl]

Added this to the Later milestone.

[kasperl]

Removed Type-Enhancement label.
Added Type-Defect label.

[kasperl]

Added TriageForM5 label.

[kasperl]

Removed TriageForM5 label.

[DartBot]

This comment was originally written by ngeoffray@google.com

---

Added Duplicate label.
Marked as being merged into #1533.