Tracking Issue for RFC2509: concat_bytes!() · Issue #87555 · rust-lang/rust (original) (raw)

Skip to content

Navigation Menu

• • GitHub Copilot Write better code with AI
  • 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

Description

Feature gate: #![feature(concat_bytes)]

This is a tracking issue for rust-lang/rfcs#2509

Public API

#[macro_export] macro_rules! concat_bytes { .. }

Steps / History

• RFC: RFC: Introduce concat_bytes!() to join [u8] and byte str analogous to concat! for str rfcs#2509
• Implementation: Implement concat_bytes! #87599
• Final comment period (FCP)
• Stabilization PR

Unresolved Questions

• Should additional literal types be supported? Byte string literals are basically the same thing as byte slice references, so it might make sense to support those as well (support &[0, 1, 2] in addition to [0, 1, 2]).
• What to do with string and character literals? They could either be supported with their underlying UTF-8 representation being concatenated, or rejected.