database/doris
2
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity

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

Browse Source 
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-24 14:51:51 +08:00
committed by GitHub
parent 6b219ab599
commit 16a394da0e
248 changed files with 1979 additions and 674 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
be/test/vec/function/function_bitmap_test.cpp
View File

@ -14,11 +14,22 @@
// KIND, either express or implied. See the License for the
// specific language governing permissions and limitations
// under the License.
#include <gtest/gtest.h>
#include <stdint.h>
#include <limits>
#include <string>
#include <vector>
#include "common/status.h"
#include "function_test_util.h"
#include "gtest/gtest_pred_impl.h"
#include "gutil/integral_types.h"
#include "testutil/any_type.h"
#include "util/bitmap_value.h"
#include "vec/functions/function_totype.h"
#include "vec/core/types.h"
#include "vec/data_types/data_type_nullable.h"
#include "vec/data_types/data_type_number.h"
#include "vec/data_types/data_type_string.h"
namespace doris::vectorized {