Jim Huang b5e26bedb1 Enforce strict include-what-you-use policy ... The include-what-you-use (IWYU) policy is beneficial to faster compilation and fewer recompilations. Many build tools, such as GNU make, provide a mechanism for automatically figuring out what .h files a .cc file depends on. These mechanisms typically look at #include lines. When unnecessary #includes are listed, the build system is more likely to recompile in cases where it is not necessary. With the enforcement, header file <include/mimalloc.h> no longer includes <stdlib.h>. Reference: https://github.com/include-what-you-use/include-what-you-use/blob/master/docs/WhyIWYU.md		2019-07-23 14:59:57 -07:00
..
mimalloc-atomic.h	avoid thread over-allocation on initial region allocations	2019-07-15 17:35:43 -07:00
mimalloc-internal.h	Use checked unsigned multiplication extension of GCC/Clang	2019-07-23 14:59:49 -07:00
mimalloc-override.h	fix to overrides on windows	2019-07-18 21:20:18 -07:00
mimalloc-types.h	Enforce strict include-what-you-use policy	2019-07-23 14:59:57 -07:00
mimalloc.h	Enforce strict include-what-you-use policy	2019-07-23 14:59:57 -07:00