I had a weird WA during Round #300 (B) for the test case 415
. I used the custom invocation tool and realized that ((int) pow(10, i))
when i=2
is equal to 99 and the number
becomes 100
instead of 101
. On my machine, the same code passed.
# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3831 |
3 | Radewoosh | 3646 |
4 | jqdai0815 | 3620 |
4 | Benq | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | gamegame | 3386 |
10 | ksun48 | 3373 |
# | User | Contrib. |
---|---|---|
1 | cry | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 160 |
5 | -is-this-fft- | 158 |
6 | awoo | 157 |
7 | adamant | 156 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | Dominater069 | 153 |
I had a weird WA during Round #300 (B) for the test case 415
. I used the custom invocation tool and realized that ((int) pow(10, i))
when i=2
is equal to 99 and the number
becomes 100
instead of 101
. On my machine, the same code passed.
Name |
---|
Never use floating point functions. If you still want to use it, make sure you round instead of cast.
I see. I should probably avoid those. Thanks!
pow works in doubles. Answer can differ because of different compilers. In this case pow(10, 2) = 99.99999..., and it casts to 99. To avoid such bugs you can add eps to result, and cast it to int only after that.
P.S. your code get AC using MS compiler: 10898670
Thank you for the explanation!
you could use power, see this AC solution 10899961
I explained it here.
Interesting. Thanks!