Damian Wieczorek

One other thought that deserves its own issue (but I'll post here first, for the record): What's the preference between using `invoke` on a `companion object` and a factory function?...

One more question on this: What about `inline` to implement a member for an abstract (or open) type? For example, Android has `LruCache` which allows override of `create(key: K)` to...

It should be clarified whether the first call should always appear on the same line. One edge case I've frequently run into: what should be done in the case where...

One other thought related to https://github.com/yole/kotlin-style-guide/issues/9#issuecomment-224664633: If the first call is to a `this`-scoped or globally-scoped function, it should be placed on the next line: ``` Kotlin val anchor =...

To improve readability, multiline single-argument lambdas should also always name the argument instead of using `it`, since `it` can become unclear in longer lambdas. ``` Kotlin // Good appendCommaSeparated(properties) {...

@cbruegg That's for sure; I had a similar feeling. I've phrased it as "prefer to first..." for that reason. While not strictly necessary in every situation, I think that repeated...

Fixing it in the IDE would be optimal solution, but would that allow developers to still explicitly namespace code? I feel like the lack of a package-private and package-protected visibility...

I agree that it's a little awkward to have the body and the class header left-aligned, but I don't think that it's worth making an exception for the opening brace...

IMO: A more natural pattern, which would be consistent with things like kotlinx-serialization, would be to support qualifier annotations directly on types. That would be a bit closer to how...

@evant Thoughts on the above? Would you be open to a PR exploring this?