Jake Wharton
Jake Wharton
This is also annoying for set bindings where I want to collect a bunch of, say, `Async` things and not really care what their generic param is.
When building from an IDE you need to enable annotation processing. Instructions for IntelliJ can be found [here](http://jakewharton.github.io/butterknife/ide-idea.html) for a similar library.
Might be a dupe of #444, except not reported as a bug in this case.
It's not clear how that test would fail as each type only contains a single field. This is an expensive operation that should have no practical effect on real code....
I would prefer that, yes.
We see this internally on scary classes that you'd never want Dagger to instantiate (e.g., android.app.Application). While we know it will never be called in practice, it's a bit unsettling...
To Dagger it's the same thing. In our impl we pass the Application instance to the constructor of the module, store it in an instance field, and return it in...
The integration tests do not work on JDK 8.
If you aren't using constructor injection can't you just do this yourself?
> There is a good reason why almost all the important Android classes are designed such that you can't construct them directly The "good reason" is that they eschew any...