Top bazel issues

Allow workspaces to reference themselves canonically

P2 feature request

Docs do not mention third_party requirements for a license

P2 documentation (cleanup)

Building on Windows

P1 other feature request

A Bazel mode for EMACS would be great to have!

P4 feature request

Document CROSSTOOL

P3 documentation (cleanup)

rule_implementation_hash is unsound when a rule definition site is a macro in b.bzl, but that macro is invoked from a.bzl, and that invocation passes along e.g. an implementation function object

P0 team-Starlark

3.4.x incompatible change: error-prone is stricter

Bazel can build different tools on different execution platforms in the same build

P1 team-Configurability feature request

Features to solve the problems with dll linking on Windows

P2 area-Windows windows team-XProduct feature request

Remove maximum path length limitation on Windows

area-Windows windows team-XProduct untriaged