Add reusable accessor method for component dependencies

[cckroets]

I have recently begun splitting my project's monolith component into smaller dagger components, using Component dependencies. I expected when pulling out dependencies from the monolith into smaller ones that the code size of the generated monolith component would decrease, but it has actually increased.

Looking through the previously generated code, whenever an object Foo was accessed to create another object the component would call a private method getFoo():

private Bar getBar() {
  return new Bar(getFoo());
} 

However now every time Foo is accessed (which has been moved to another component), the precondition check is called inline:

private Bar getBarCreator() {
  return new Bar(Preconditions.checkNotNull(DaggerMonolithComponent.this.otherComponent.foo(), "Cannot return null from a non-@Nullable component method"));
} 

This same code block is duplicated hundreds of times in the component leading to longer code generation time and longer compilation time. Can we add a build optimization to generate a private accessor method that does this safety check for each component dependency used?

[Chang-Eric]

Thanks, I think this is a reasonable optimization to do.