commit 377314b83daef2ff031b6228ce582790204540eb
author UebelAndre <github@uebelandre.com> Tue Feb 20 02:19:55 2024 -0800
committer GitHub <noreply@github.com> Tue Feb 20 10:19:55 2024 +0000
tree 70154fc7925184b84b331be61909880fc4b3744f
parent b1fc85232d17c95d7f558adc3607a99871db9553

Allow rules to provide their own rust-analyzer providers (#2487)

This change cleans up the rust-analyzer aspect to support external rules
providing their own crate specs. For now only prost implements behavior
for this and the rust-analyzer interface is still private. In the future
if this proves to be performant and a consistent interface then there
should be no issue making this a public part of the `//rust` package.

This change incorporates
https://github.com/bazelbuild/rules_rust/pull/1875 (special thanks to
@snowp!) and addresses performance issues in the generator tool by
allowing users of `bazelisk` to ensure their `tools/bazel` scripts run
should one be provided and to disable running validation actions when
building crate specs.