torgil

From experience, I think go's choice of random iteration order could flush out some un-necessary bugs. https://nathanleclaire.com/blog/2014/04/27/a-surprising-feature-of-golang-that-colored-me-impressed/

@googlebot I signed it!

> We also need this functionality added to bazel. > Can we get a confirmation that it will be merged? You also may want this to be able to pick...

Yes. We're doing custom rules using cc_common interface. InstrumentedFilesInfo is not available from there. For these kind of files it for me looks cleaner if the featue or rule specifying...

> > We also need this functionality added to bazel. > > Can we get a confirmation that it will be merged? > > You also may want this to...

> > Yes. We're doing custom rules using cc_common interface. InstrumentedFilesInfo is not available from there. > > Why not? Is Bazel not making the API available to you to...

Ping @oquenchil We have also a need of making the .d - file and the .su - file available to Starlark after compilation for header coverage tests and other tests...

I've rebased this patch on master (5.0 prereleases), it required updates for gcno-files to show up using the "build" command. edit: Github UI seems broken as it doesn't update this...

Rebased versions of coverage patches + additional essential patches can be found here: https://github.com/torgil/bazel/commits/master

@avielas > https://docs.bazel.build/versions/main/command-line-reference.html#flag--collect_code_coverage The gcno-files are generated during compilation (not during test) and are already available in CcCompilationOutputs. They are just not accessible from Starlark which is what this patch...