Missing documentation/feature - changing global_allocator in cargo test

[Firstyear]

Hi,

From https://github.com/rust-lang/rust/blob/master/library/core/src/alloc/global.rs#L5 this mentions how to use a different global allocator in the main of a binary. It would be beneficial to be able to use the same allocator in tests of that binary, or associated libraries and modules.

Can this documentation be extended to demonstrate how cargo test can use an alternate allocator? Alternately if this isn't possible today, can this be a feature request to allow the allocator to be changed with cargo test?

Thanks,

[ghost]

Yeah I was also looking for the actual same thing.

[ehuss]

Can you clarify why it doesn't seem the allocator is not used in your test? If you place a #[test] function in main.rs, and run cargo test, that test should use the global allocator defined in main.rs.

If you have a lib.rs, then you can move the #[global_allocator] to the lib.rs, and all Cargo tests (and binaries) should inherit that. The allocator needs to be defined once (and only once) somewhere in the dependency graph, and where it goes depends on what you are doing.

Generally the std docs don't discuss Cargo directly, since the docs are somewhat agnostic to the build tool (and generally that level of detail belongs to guide-style material).

[Firstyear]

@ehuss I think what I'm asking is that that behaviour should be explicitly documented in the global allocator trait page as today it's ambiguous to how you use a custom allocator in tests. Alternately, it could be added to https://doc.rust-lang.org/edition-guide/rust-2018/platform-and-target-support/global-allocators.html