#include <bits/stdc++.h>在 C++ 中工作?

How does #include lt;bits/stdc++.hgt; work in C++?(#include lt;bits/stdc++.hgt;在 C++ 中工作?)
本文介绍了#include <bits/stdc++.h>在 C++ 中工作?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着跟版网的小编来一起学习吧!

问题描述

我从 codeforces 博客中了解到,如果我们添加 #include <bits/stdc++.h>C++ 程序中,则不需要包含任何其他头文件.#include #include 是如何工作的,是否可以使用它而不是包含单个头文件?

I have read from a codeforces blog that if we add #include <bits/stdc++.h> in a C++ program then there is no need to include any other header files. How does #include <bits/stdc++.h> work and is it ok to use it instead of including individual header files?

推荐答案

它基本上是一个头文件,还包括每个标准库和 STL 包含文件.我能看到它的唯一目的是测试和教育.

It is basically a header file that also includes every standard library and STL include file. The only purpose I can see for it would be for testing and education.

参见例如GCC 4.8.0/bits/stdc++.h 源码.

使用它会包含很多不必要的东西并增加编译时间.

Using it would include a lot of unnecessary stuff and increases compilation time.

正如尼尔所说,它是预编译头的实现.如果您正确地将它设置为预编译,它实际上可以根据您的项目加快编译时间.(https://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html)

As Neil says, it's an implementation for precompiled headers. If you set it up for precompilation correctly it could, in fact, speed up compilation time depending on your project. (https://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html)

但是,我建议您花时间了解每个 sl/stl 标头并单独包含它们,并且除了预编译目的之外不要使用超级标头".

I would, however, suggest that you take time to learn about each of the sl/stl headers and include them separately instead, and not use "super headers" except for precompilation purposes.

这篇关于#include &lt;bits/stdc++.h&gt;在 C++ 中工作?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!

本站部分内容来源互联网,如果有图片或者内容侵犯了您的权益,请联系我们,我们会在确认后第一时间进行删除!

相关文档推荐

Prevent class inheritance in C++(防止 C++ 中的类继承)
Why should I declare a virtual destructor for an abstract class in C++?(为什么要在 C++ 中为抽象类声明虚拟析构函数?)
Why is Default constructor called in virtual inheritance?(为什么在虚拟继承中调用默认构造函数?)
C++ cast to derived class(C++ 转换为派生类)
C++ virtual function return type(C++虚函数返回类型)
Is there any real risk to deriving from the C++ STL containers?(从 C++ STL 容器派生是否有任何真正的风险?)