Kotlin+Dagger best practices/documentation/pain points
Opening this as a tracking bug for all kotlin related documentation that we should be add/best practices that we should call out to make using Dagger w/ Kotlin easier. One example: How to achieve the effect of `static @Provides` in Kotlin. Feel free to comment new ideas, but don't make "me too" or "i agree with XYZ" comments.
Posted by ronshapiro on Oct 15, 2017, 3:27 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Kotlin+Dagger best practices/documentation/pain points
Opening this as a tracking bug for all kotlin related documentation that we should be add/best practices that we should call out to make using Dagger w/ Kotlin easier. One example: How to achieve the effect of `static @Provides` in Kotlin. Feel free to comment new ideas, but don't make "me too" or "i agree with XYZ" comments.
Comments (0)
No comments yet. Start the discussion.