rust-lang / rust-lang/rust

Tracking Issue for c-char-type

Open
#138,446 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-rust-for-linux C-tracking-issue T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for the -Zc-char-type='unsigned|signed|default' (configurable c_char override to i8/u8).
The feature gate for the issue is #![feature(c_char_type)].

Requested by Rust-For-Linux as gcc/clang -funsigned-char analog: https://github.com/Rust-for-linux/linux/issues/355.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
Unresolved Questions
Implementation history

Implementation PR: https://github.com/rust-lang/rust/pull/138290

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with implementation PR 138290, then read the rustc-dev-guide stabilization and documentation instructions linked in the issue. Check the Style Guide and nightly-style procedure for the required formatting work. Done means the implementation, documentation, formatting, and stabilization checklist items are complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.