|
Jul
18 |
|
comment |
Wait, ASCII was 128 characters all along? nice catch to the both of you! |
|
Jul
18 |
|
revised |
Wait, ASCII was 128 characters all along? -10 bytes |
|
Jul
18 |
|
awarded | Commentator |
|
Jul
17 |
|
answered | Wait, ASCII was 128 characters all along? |
|
Jul
17 |
|
comment |
Wait, ASCII was 128 characters all along? f(n>>7) is shorter by 2 bytes :) |
|
Jul
17 |
|
comment |
Wait, ASCII was 128 characters all along? my bad, but thank you for the longer one. |
|
Jul
17 |
|
comment |
Wait, ASCII was 128 characters all along? at present all test cases have the critical character at the end, so 127>number%128>31 passes all those tests without actually answering the challenge. can you provide test cases where the last character is printable but an earlier one isn't? |
|
Jul
17 |
|
awarded | Nice Answer |
|
Jul
16 |
|
revised |
Create a Pride Flag -14 bytes |
|
Jul
16 |
|
awarded | Yearling |
|
Jul
16 |
|
awarded | Yearling |
|
Jul
16 |
|
comment |
Constructing the interval [0, 1) via inverse powers of 2 This is a known problem, because this is how IEEE754 represents these numbers. 1/3 is famously not representable exactly using floats, no matter the precision. |
|
Jul
16 |
|
awarded | Yearling |
|
Jul
16 |
|
awarded | Yearling |
|
Jul
16 |
|
awarded | Yearling |
|
Jul
16 |
|
answered | Solution for a modern nation that mustn't see themselves or their own reflection |
|
Jul
15 |
|
revised |
Compare version numbers -5 bytes, fix regex |
|
Jul
15 |
|
revised |
Compare version numbers fix all test cases to turn this into a competing answer |
|
Jul
15 |
|
revised |
o y u (or and or) -2 bytes |
|
Jul
12 |
|
answered | Compare version numbers |