Richard Levasseur

Add fail.format() to make it easier to use formatted strings with fail()

4

### Description of the feature request: Make it easier to produce nice looking error messages with `fail()`. So we can write this: ``` fail.format( "Unable to find interpreter '{name}' for...

Create a last-green branch to track the latest green commit

2

### Description of the feature request: When building Bazel, it's not uncommon for HEAD to be broken. That it's broken isn't a big deal, but it does create a barrier...

Support None values

2

Support for None is very spotty. I think IntSubject supports it, maybe string, but not all of them. None doesn't happen much in rule code per-se, more so in utility...

While asserting some runfiles, I needed to do something like: ``` target.runfiles().contains_at_least([ , ]) ``` Unfortunately, there isn't a great way to do this. At the least, I think these...

There's a few accessors that strings have that would make using StrSubject a bit easier: * startswith * endswith Also expose `.actual` to easily get at the actual value. This...

Show diff for large objects

1

When large objects are compared, it makes the resulting errors hard to visually see what the differences are. This occurs with both large strings (e.g. generated BUILD file content for...

The `matches` method is to make it easier to check strings without checking exact equality. The basic API accepts two types: * A Matcher object (e.g. `matching.str_matches`) * A string,...

Today, if you're testing a rule that returns `platform_common.ToolchainInfo`, getting at the value is a bit awkward -- ToolchainInfo is a single provider type, but it carries toolchain-specific attributes. The...

feat: compile source files at build time

1

This implements precompiling: performing Python source to byte code compilation at build time. This allows improved program startup time by allowing the byte code compilation step to be skipped at...