Closed RossComputerGuy closed 10 months ago
I don't think this field should even have a default value, the user should be forced to use an allocator. This matches how the entire standard library works and prevents any performance hiccups from unknowingly using the page allocator.
I don't think this field should even have a default value, the user should be forced to use an allocator. This matches how the entire standard library works and prevents any performance hiccups from unknowingly using the page allocator.
Yea, I agree. And since the defaulting breaks certain platforms I see no reason to keep this allocator default.
I am working on a project which uses clap in UEFI and having the default allocator in the structs is causing this error despite me overriding the allocator.
Best option is to make the allocator nullable and doing an
orelse
on it.