I've seen many people writing many header files explicitly and not using bits/stdc++.h. Does using bits/stdc++.h have any disadvantages?
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 3985 |
2 | jiangly | 3814 |
3 | jqdai0815 | 3682 |
4 | Benq | 3529 |
5 | orzdevinwang | 3526 |
6 | ksun48 | 3517 |
7 | Radewoosh | 3410 |
8 | hos.lyric | 3399 |
9 | ecnerwala | 3392 |
9 | Um_nik | 3392 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 169 |
2 | maomao90 | 162 |
2 | Um_nik | 162 |
4 | atcoder_official | 161 |
5 | djm03178 | 158 |
6 | -is-this-fft- | 157 |
7 | adamant | 155 |
8 | awoo | 154 |
8 | Dominater069 | 154 |
10 | luogu_official | 150 |
I've seen many people writing many header files explicitly and not using bits/stdc++.h. Does using bits/stdc++.h have any disadvantages?
Название |
---|
It works in GCC only and there are probably no guarantees that it will still work in the future. It also slows down compilation as compiler has to process much more files (unless you use it as intended — as a precompiled header, see below). There are several other downsides, they all sum up to "it's unacceptable in production code".
Note that when setup correctly, it would make compilation faster.
In my MacBook Pro with
g++-7
, compile a HelloWorld program using precompiled<bits/stdc++.h>
is ~15% faster than<iostream>
.That people, as I think, use XCode (IDE) on MacOS. It IDE hasnt <bits/stdc++.h> header. P.S. it just my hypothesis and sorry for my ENG.
People who code in visual studio don't use it because it doesn't work there. Other reasons:
It slows down compilation time(doesn't affect execution time though)
On few OJs, Variable name y1 doesn't work with it. Example How to avoid it
It's hard to memorize?
A Noob like me sometimes write #include<bits\stdc++.h> And then it's hard to debug the error...
Ps: I don't do this now.. but it happened to me once.