https://issues.dlang.org/show_bug.cgi?id=19432

Stanislav Blinov <stanislav.blinov@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stanislav.blinov@gmail.com

--- Comment #1 from Stanislav Blinov <stanislav.blinov@gmail.com> ---
That needs an "U" suffix, which is a little bit not obvious from the spec:

https://dlang.org/spec/lex.html#integerliteral

--

https://issues.dlang.org/show_bug.cgi?id=19432

johanengelen@weka.io changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from johanengelen@weka.io ---
Indeed, thanks.  Specifically 2.12.8

--

https://issues.dlang.org/show_bug.cgi?id=19432

Răzvan Ștefănescu <rumbu@rumbu.ro> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
                 CC|                            |rumbu@rumbu.ro
         Resolution|INVALID                     |---

--- Comment #3 from Răzvan Ștefănescu <rumbu@rumbu.ro> ---
I don't consider this resolved. Unsigned long values were accepted before without error, I cannot tell for sure when this changed.

ulong x = 9223372036854775809; was considered valid code.

I don't see the point in forcing the user to decorate his numbers with data type suffixes.

--

https://issues.dlang.org/show_bug.cgi?id=19432

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |pull

--- Comment #4 from Dlang Bot <dlang-bot@dlang.rocks> ---
@benjones created dlang/dmd pull request #10607 "fix issue 19432 automatically interpret big int literals as " fixing this issue:

- fix issue 19432 automatically interpret big int literals as unsigned longs if they dont fit in a signed long

https://github.com/dlang/dmd/pull/10607

--

https://issues.dlang.org/show_bug.cgi?id=19432

--- Comment #5 from Dlang Bot <dlang-bot@dlang.rocks> ---
@benjones created dlang/dlang.org pull request #2718 "fix issue 19432 automatically interpret big int literals as " fixing this issue:

- fix issue 19432 automatically interpret big int literals as unsigned longs if they dont fit in a signed long

https://github.com/dlang/dlang.org/pull/2718

--

https://issues.dlang.org/show_bug.cgi?id=19432

Dlang Bot <dlang-bot@dlang.rocks> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #6 from Dlang Bot <dlang-bot@dlang.rocks> ---
dlang/dlang.org pull request #2718 "fix issue 19432 automatically interpret big int literals as " was merged into master:

- ca4a016638b47d755c1e7d196b8bafeb2f023803 by Ben Jones:
  fix issue 19432 automatically interpret big int literals as unsigned longs if
they dont fit in a signed long

https://github.com/dlang/dlang.org/pull/2718

--

https://issues.dlang.org/show_bug.cgi?id=19432

--- Comment #7 from Dlang Bot <dlang-bot@dlang.rocks> ---
dlang/dmd pull request #10607 "fix issue 19432 automatically interpret big int literals as " was merged into master:

- b9443805651c40bb56250c195a3de70c9cdaa2f3 by Ben Jones:
  fix issue 19432 automatically interpret big int literals as unsigned longs if
they dont fit in a signed long

https://github.com/dlang/dmd/pull/10607

--