Tracking Issue for `is_assigned` and `is_private_use` methods on `char`
Open
Nobody has claimed this yet.
C-tracking-issue
S-tracking-needs-to-bake
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(char_unassigned_private_use)]
This is a tracking issue for the is_assigned and is_private_use methods on char.
Public API
// core
impl char {
pub fn is_assigned(self) -> bool;
pub const fn is_private_use(self) -> bool;
}
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- Implementation: https://github.com/rust-lang/rust/pull/157946
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
@rustbot label -S-tracking-unimplemented S-tracking-needs-to-bake
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The implementation is tracked in rust-lang/rust#157946; start by reviewing that PR and the linked stabilization guide. The issue is complete when the final comment period and stabilization PR steps are finished, with no unresolved questions remaining.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100