[chore](build) Use include-what-you-use to optimize includes (PART II) (#18761)

Currently, there are some useless includes in the codebase. We can use a tool named include-what-you-use to optimize these includes. By using a strict include-what-you-use policy, we can get lots of benefits from it.
This commit is contained in:
Adonis Ling
2023-04-19 23:11:48 +08:00
committed by GitHub
parent c40860aba4
commit e412dd12e8
1225 changed files with 14114 additions and 3020 deletions

View File

@ -15,7 +15,15 @@
// specific language governing permissions and limitations
// under the License.
#include <algorithm>
#include <boost/iterator/iterator_facade.hpp>
#include <utility>
#include "vec/core/types.h"
#include "vec/data_types/data_type.h"
#include "vec/data_types/data_type_nullable.h"
#include "vec/data_types/data_type_number.h"
#include "vec/data_types/data_type_time_v2.h" // IWYU pragma: keep
#include "vec/functions/date_time_transforms.h"
#include "vec/functions/function_date_or_datetime_to_something.h"
#include "vec/functions/simple_function_factory.h"
@ -117,4 +125,4 @@ void register_function_time_of_function(SimpleFunctionFactory& factory) {
factory.register_alternative_function<FunctionWeekDayV2Old>();
factory.register_alternative_function<FunctionDateTimeV2WeekDayOld>();
}
} // namespace doris::vectorized
} // namespace doris::vectorized