Justin

We should not use `toString` for business logic. `toString` should only be used to generate debugging strings. This is not the proper solution for #28695. Approaches to solve that issue...

At the very least, we need to update the `equals` method to use the same definition of equality that `hashCode` uses. So, if `hashCode` keys off of `type.getName().hashCode()`, then equals...

@bot-gradle test this

Blocked by https://github.com/android/nowinandroid/issues/1433

@bot-gradle test apt

@bot-gradle test this

This exposes the same types you can get from a configuration, so files, artifacts, and the root variant of a resolution result. This is part of an effort to eventually...

One downside to resolution result is that the whole type is not lazy or cc compatible. Only getRootComponent is. This type exposes only CC compatible and lazy results

In practice ResolutionResult is and will continue to be relevant. RR provides access to the resolved graph via the root component. Future APIs will provide access to the graph via...

There is no timeline to when this new API will be introduced. Until then RR will remain fully supported. We expect the transition to remain simple, as both APIs expose...