It looks like

1.0.0-beta-1103

still generates more methods than

M14

used to do

We have about 700 methods of overhead when compiled against

1.0.0-beta-1103

compared to

M14

and all extra methods come from lamba expressions used with delegated properties

I was wrong about lambda expressions, the issue has nothing to do with them

each delegated property generates an additional class

with a meta information about the property

Is there a way to add the equivalent of a companion extension to a java class?

I see nothing related to this on the documentation page: https://kotlinlang.org/docs/reference/extensions.html

no, static extensions for Java classes are not currently supported. we’ve wanted to have them in some cases, so they are likely to appear in the future.

is there a convenient way to invoke KDoc from the IDE?

KDoc as in the documentation generation tool?

yes

is there another KDoc? simple smile

KDoc is also the documentation format

KDoc the tool is dead and does not exist any more

um …… ok. so, the only way to view KDoc actually formatted is in IntelliJ itself via the quick lookup windows?

It would be so awesome if KDoc supported Asciidoc instead or alongside Markdown

its replacement is dokka: https://github.com/kotlin/dokka

@Czar: why? which exactly asciidoc features do you want to use in your documentation?

ah, i see

@yole I use asciidoc to write reference documentation for my projects and for java there is asciidoc doclet so I can use asciidoc instead of javadoc, that way it is much easier to import java api docs into reference documentation to avoid duplication.

as for features, we could plunge into the holy war on 'asciidoc vs markdown' topic, but I'll just say that many prefer one to another.

I think asciidoc understands enough of markdown syntax to be able to digest doc comments written using markdown syntax

I don't believe that to be the case.

tables, codeblocks, etc.

how often do you use tables in doc comments?

well, not everyday but sometimes and codeblocks - all the time.

the actual reason why asciidoc isn’t going to be supported in the foreseeable future is that our tools need to be able to parse and understand the syntax of the doc comments