From what I have just learned, the `global_allocator` attribute has some magic: it can be used anywhere to define a global allocator, even deep inside a private unused module of a dependency of a dependency the defined global allocator will be called implicitly, i.e., your crate will be affected if it has a dependency which defines the global allocator, even if your crate doesn’t call any function from that dependency as far as I know, there is no way to check what global allocator I’m us...
