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
Skipped test in S02-types/nan.t for 'NaN ** 0' #3804
Comments
From @usev6There is a test for 'NaN ** 0' returning 0 in S02-types/nan.t skipped for the reason 'unspecced and inconsistent'. Also there is a comment above the test: # if we say that 0**0 and Inf**0 both give 1 (sse below), then for which MoarVM and JVM agree with that last suggestion: < bartolin> r: say NaN ** 0 As far as I understand it, that is in line with the IEEE 754 Standard 2008 (e.g. http://stackoverflow.com/questions/17863619/why-does-nan0-1). I'm inclined to change the test accordingly (expecting 1 as the result) and unfudge it. Any opinions? |
1 similar comment
From @usev6There is a test for 'NaN ** 0' returning 0 in S02-types/nan.t skipped for the reason 'unspecced and inconsistent'. Also there is a comment above the test: # if we say that 0**0 and Inf**0 both give 1 (sse below), then for which MoarVM and JVM agree with that last suggestion: < bartolin> r: say NaN ** 0 As far as I understand it, that is in line with the IEEE 754 Standard 2008 (e.g. http://stackoverflow.com/questions/17863619/why-does-nan0-1). I'm inclined to change the test accordingly (expecting 1 as the result) and unfudge it. Any opinions? |
From @lizmat
+1 Liz |
From @masakbartolin (>):
+1 |
The RT System itself - Status changed from 'new' to 'open' |
From @usev6On Mon May 18 13:19:37 2015, bartolin@gmx.de wrote:
I changed the test (and a second test for the same thing in S32-num/power.t) with commit Raku/roast@a30ffc1ed0 I'm closing this ticket as 'resolved'. |
1 similar comment
From @usev6On Mon May 18 13:19:37 2015, bartolin@gmx.de wrote:
I changed the test (and a second test for the same thing in S32-num/power.t) with commit Raku/roast@a30ffc1ed0 I'm closing this ticket as 'resolved'. |
@usev6 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#124450 (status was 'resolved')
Searchable as RT124450$
The text was updated successfully, but these errors were encountered: