# | User | Rating |
---|---|---|
1 | tourist | 3993 |
2 | jiangly | 3743 |
3 | orzdevinwang | 3707 |
4 | Radewoosh | 3627 |
5 | jqdai0815 | 3620 |
6 | Benq | 3564 |
7 | Kevin114514 | 3443 |
8 | ksun48 | 3434 |
9 | Rewinding | 3397 |
10 | Um_nik | 3396 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | Um_nik | 163 |
3 | maomao90 | 162 |
3 | atcoder_official | 162 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 155 |
8 | TheScrasse | 154 |
9 | Dominater069 | 153 |
10 | djm03178 | 152 |
Name |
---|
Maybe it is because
pow
?I tried 'GNU C++17 (64)',and it returned
WA
too.Since the pow function uses and returns double value, with big numbers it can have a slight error, which gave you the WA verdict (You can see in your C++20 submission, the answers are only off by 16: 101159538130177904 vs 101159538130177920). I converted the types to long double and it got accepted: 173634899
For why did the C++17 solution get accepted, I have no idea. Maybe it's because of their different ways of compiling code?
More on this, you shouldn't use the pow function for integers for the same reason: Instead of pow(a, 2), it's recommended to use a*a. Your same code using a*a: 173635181
I think this is precisely what you are experiencing.
Yes. Floating point numbers work in mysterious ways in C++(32 bit). With C++(64 bit) they behave a lot more sane.
For example submitting
gives AC with C++17(32 bit) 173799443.
While submitting
gives WA with C++17(32 bit) 173799415.
Dealing with floating point numbers in C++(32 bit) almost feels like quantum physics. Just looking at them can change the result.