View all comments

PR #156882 is stabilizing Allocator.

In order to do so more easily, it's marking Allocator as not dyn-compatible, to reserve the options of either adding features that currently prevent dyn-compatibility or marking it dyn-compatible and requiring those features to use an extension trait instead.

In order to make this decision and the stabilization decision in parallel, I'm filing this issue for a separate FCP.

Based on the discussion in the All Hands, it seemed like there weren't any features that we couldn't do via the extension trait solution, allowing the base trait to be dyn-compatible. So, in this issue, I'm proposing that we remove the limitation on Allocator and allow dyn Allocator.