Tracking issue for placement new · Issue #27779 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • GitHub Models New Manage and compare prompts
  • GitHub Advanced Security Find and fix vulnerabilities
  • Actions Automate any workflow
  • Codespaces Instant dev environments
  • Issues Plan and track work
  • Code Review Manage code changes
  • Discussions Collaborate outside of code
  • Code Search Find more, search less
• Explore
  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights
• • GitHub Sponsors Fund open source developers
  • The ReadME Project GitHub community articles
• • Enterprise platform AI-powered developer platform
• Pricing

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sign up

Appearance settings

Description

This is a tracking issue for the unstable placement_new_protocol feature in the standard library, and placement_in_syntax/box_syntax in the compiler.

(@pnkfelix adds below:)

Things to decide / finalize before stabilization:

• placement-in syntax, e.g. in PLACE { BLOCK } vs PLACE <- EXPR. (See Place left arrow syntax (place <- expr) rfcs#1228 )
• protocol interface, e.g. passing &mut self vs self for the Placer::make_place (Placement protocol should not consume Placer rfcs#1286).
• Is a desugaring box EXPR part of this? (currently the desugaring doesn't work due to type inference issues).
• Factor a common Place for InPlace and BoxPlace, or just have the InPlace trait independently from any BoxPlace.