bazelbuild / bazelbuild/bazel

Promote --experimental_cc_implementation_deps to not be experimental

Open
#20,098 14 comments 3 reactions 0 assignees View on GitHub
P3 team-Rules-CPP type: feature request
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

### Description of the feature request:

This feature is flipped by default in master and also in 6.4. It would make sense to remove the experimental name from it.

During BazelCon 2023 I had a 1 to 1 with people from the C++ team and I understood that they are not aware of any current blocker in order to remove the experimental part of the name.

### Which category does this issue belong to?

C++/Objective-C Rules

### What underlying problem are you trying to solve with this feature?

_No response_

### Which operating system are you running Bazel on?

_No response_

### What is the output of `bazel info release`?

_No response_

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Contributor guide

Open the contributing guide

Research direction

Search the repository for the exact --experimental_cc_implementation_deps flag and inspect its C++/Objective-C rule references, documentation, and tests. Confirm the feature is already enabled by default in master and 6.4, then update the remaining experimental naming and verify the affected tests and documentation no longer use it.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, objective-c
Domain
build-system
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.