Skip to content

Conversation

phip1611
Copy link
Member

The allocator_api feature [0] is old and not developed in years. Since then, understanding of memory safety and best practises has evolved. It is unlikely that in its current form the functionality will ever be merged.

Therefore, we drop the complexity we have from this feature for now, leading to simpler code.

[0] rust-lang/rust#32838

Checklist

  • Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
  • Update the changelog (if necessary)

@phip1611 phip1611 self-assigned this Sep 13, 2025
@phip1611 phip1611 force-pushed the allocator branch 2 times, most recently from d6c7c1d to 981f067 Compare September 13, 2025 08:47
The allocator_api feature [0] is old and not developed in years. Since
then, understanding of memory safety and best practises has evolved.
It is unlikely that in its current form the functionality will ever
be merged.

Therefore, we drop the complexity we have from this feature for now,
leading to simpler code.

[0] rust-lang/rust#32838
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant