rust-lang / rust-lang/rfcs

[Feature Request] compile time arguments

Open
#2,785 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Markdown
Stars
6.6k
Forks
1.7k
Avg merge
16h 14m
Merged PRs (30d)
1

Description

Currently the closest thing to C's preprocessor conditional compilations we have is the cfg and the features.

But there's one missing piece, and that's and that's values in those variables.

Currently the design idea of features is to be incremental which doesn't make sense with having values in those features.
The thing is that in practice a lot of crates don't really use features as incremental and have mutually exclusive features.

I understand that the incremental features idea is rooted pretty deep in cargo's dependency resolvement.
Is there a way to have this without a big problem with having the same dependency twice in the dependency graph but with different values?
Could we maybe have some symbol randomness and just treat them as two different libraries?

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or entry points are named. Start by examining the issue's discussion of cfg, features, and Cargo dependency resolution, then determine whether value-bearing compile-time arguments can fit the incremental feature model. Done would require a concrete design and resolution for dependencies with different values, which the issue does not define.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system, compilers
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.