Keith Smiley

With this code: ```swift class Store { var currentState: State { fatalError() } } class CompositeStore: Store { let store: (repeat Store) let combine: ((repeat (each State)) -> CompositeState) override...

This code compiles: ```swift class Store { var currentState: State { fatalError() } } class CompositeStore: Store { let store: (repeat Store) let combine: ((repeat (each State)) -> CompositeState) override...

If your command opening a file contained some regex such as: ``` grep -iqE '^[^TXZ ]+ +(\S+\/)?g?(view|n?vim?x?)(diff)?$' foo.txt ``` The json would fail to pretty print because of the invalid...

In the release configuration debugging can fail in some cases, I assume this wasn't intentional

This allows you to ignor specific event types when you potentially only care about specific events like execs.

This is useful for compact viewing as if you had run each command from the command line. I think this is more glanceable and grep-able when you're investigating specific commands.

This removes the dependency on the C++ dylib and makes the necessary API updates

Documentation search results shows duplicates

1

### Page link: https://bazel.build/versions/6.2.0/rules/lib/rule_attributes?hl=en ### Problem description (include actual vs expected text, if applicable): Example searching for "rule" ### Where do you see this issue? (include link to specific section...

This slightly improves https://github.com/bazelbuild/bazel/issues/21391

Improve error for mismatched local_jdk version in tests

1

### Description of the bug: When working on bazel itself, some shell tests like `//src/test/tools/bzlmod:verify_default_lock_file` depend on the local_jdk through this script: https://github.com/bazelbuild/bazel/blob/31fae9e8e6687cbaf0dfe55a466696210c80be96/src/test/shell/testenv.sh.tmpl#L95 In the case your installed JDK mismatches...