Document future of this ruleset
jsharpe opened this issue · 2 comments
This proposal: https://docs.google.com/document/d/1GW7UVo1s9X0cti9OMgT3ga5ozKYUWLPk9k8c4-34rC4/edit# suggests that rules_cc is going to at least stagnate in development as an internal to Bazel migration occurs.
It'd be useful to document at least some ideas of what the future for rules_cc might be so potential users understand whether they should be using this or @bazel_tools//cpp
rules if they want to integrate with the Bazel starlark rules for C/C++
Sure would be nice to get some clarification here to resolve whether we should be applying the lint rule from buildifier or not...
There seem to be quite a few bazel design docs out there with uncertain statuses, including e.g. the dependencies overhaul and licensing rules documents. Sure would be nice if the public-facing ones included a line about their status, similar to PEPs. It does seem like the bazel native cc rules aren't going anywhere any time soon, though.