Jake Wharton
Jake Wharton
Here's my idea: a reverse `BufferedSource.peek()`. You `buffer()` a `CodeWriter` and write whatever you want to it but it goes to a `StringBuilder` not the real `Appendable`. Then, you inspect...
It doesn't need to wait. ```kotlin @JvmName("jvmModifiers") @Deprecated(level = HIDDEN) fun jvmModifersOld(..) { .. } @JvmName("jvmModifiersNew") fun jvmModifers(..): Builder { .. } ```
> Wouldn't it break implicit returns in Kotlin though? Yes it is source incompatible but literally (and not hyperbolically) no one is relying on this. It would have to be...
It's allowed in bytecode, not source code.
May want to consider Metalava instead which makes an effort to _also_ ensure source compatibility and can work for targets other than the JVM.
android-ktx used it when it was on GitHub. It's just a project that poops out a jar like any other. Wire it up to a JavaExec and you're good to...
I certainly like the results. When do you emit a parameter spec with wrapping=False?
Ah, nice. I think I'd prefer if we flipped the boolean so that it wraps by default and we opt-out only in the lambda special case.
You'll have to rewrite my commit to use `[email protected]` as the author email for the CLA check to pass. Or feel free to just squash my commit into yours–I don't...
Heh, I was upgrading from 0.41 😄