-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native uint doesn't overflow on ++ #4989
Comments
From @JuerdBug: > my uint8 $x = 255; print $x, " -> "; $x = $x + 1; say $x; Work as expected: > my uint8 $x = 256; say $x I'd like to contribute tests for this; where in roast should I put them? Juerd Waalboer <juerd@tnx.nl> |
From @skidsS02-types/native.t would seem a ood place for testing scalar sized uints. A couple blocks below the tests for 124084 are some comparable tests. |
The RT System itself - Status changed from 'new' to 'open' |
From @JuerdJuerd Waalboer skribis 2016-01-04 0:25 (+0100):
Ahem, that's not the bug. This is: > my uint8 $x = 255; print $x, " -> "; $x++; say $x; Juerd Waalboer <juerd@tnx.nl> |
From @JuerdBrian S. Julin via RT skribis 2016-01-03 15:37 (-0800):
Thanks. Unfortunately, I couldn't easily figure out how to write TODO # RT #127144, uint increment in sink context Juerd Waalboer <juerd@tnx.nl> |
From @lizmat
t/spec/S02-types/native.t probably. Liz |
From @bdwJust speculating, but I think this can be fixed by codegen; to be specific, 2016-01-04 11:37 GMT+01:00 Elizabeth Mattijsen <liz@dijkmat.nl>:
|
From @lizmat
What is the bug here??? Looks to me it’s entirely doing what is expected? Liz |
From @FROGGSThat highlights the bug: m: my uint8 $x = 255; print $x, " -> "; $x = $x + 1; say $x; m: my uint8 $x = 255; print $x, " -> "; $x++; say $x; Am 04.01.2016 um 11:48 schrieb Elizabeth Mattijsen:
|
From @AlexDanielThis no longer prints 256. Bisectable points to rakudo/rakudo@5401a1a Is it actually resolved or not? I will mark it testneeded for now (if it's not resolved, the tests should reveal it). On 2016-01-04 04:14:49, FROGGS.de wrote:
|
From @dogbert17On Fri, 07 Apr 2017 19:16:17 -0700, alex.jakimenko@gmail.com wrote:
Turns out the the tests listed above where added to roast with |
@dogbert17 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#127144 (status was 'resolved')
Searchable as RT127144$
The text was updated successfully, but these errors were encountered: