Hey all. We're starting to land some Kotlin-specific changes into Dagger! Two have already landed w...

# dagger

[jw]

Hey all. We're starting to land some Kotlin-specific changes into Dagger!

Two have already landed which will be in the next release:
- Understand qualifier annotations on properties without requiring a use-site target (i.e., @Whatever instead of @field:Whatever)
- Understand @Module on object does not require a module instance.

We have a few more in the pipeline, but if you have any ideas of small ergonomic improvements like this please file an issue on GitHub.

[zachtib]

Is there any chance of ever getting to @Inject annotate the class declaration in order to specify the default constructor rather than having to break the constructor out?

[jw]

The @Inject annotation does not allow targeting to types. You'd probably have better luck getting Kotlin to add an annotation use-site target for the primary constructor for class-level annotations.

[zachtib]

gotcha, would that be something to post on their YouTrack?

[jw]

Yes

[zachtib]

Thanks. Happy to see some Kotlin QoL improvements in Dagger, though!

[arekolek]

So the second one is about static provides?

[jw]

Yes. Providers on an object will be interpreted as "static" without needing @JvmStatic.

[jw]

The generated code now knows to call Whatever.INSTANCE.method() in that case.

[jw]

And then R8 has a staticization pass which will likely eliminate the INSTANCE altogether and make them static in bytecode anyway. More details on that at https://jakewharton.com/r8-optimization-staticization/

[gildor]

The need for @JvmSuppressWildcards is significantly decrease ergomonics, especially for lambdas

[jw]

That's next on my list. Well, first. The listed two things were done by someone else.

[gildor]

typealias as qualifier, but it, I believe, already was reported

[jw]

Yeah I'm not sure I quite buy that one

[gildor]

Yeah, also not sure about backward compatibility with existing code, but looks still nice to have super simple way to declare qualifiers. But anyway, looks that we use @Named much more than annotation because of multi-module project

[Paul Woitaschek]

Rename component and module into something less ambiguous 😉