(for example they recently removed the requirement for significant newlines, it was never a high priority)

well, remember it started out as the “simple build tool” but once The Monster broke free of the lab they had to rebrand

i don’t think much thought went into it at all.

Agreed.

I think it’s a textbook illustration of someone jumping into a field who knows more about the language of implementation than the field.

It’s great to scratch an itch and a fantastic way to learn

but it produces tools that are far from meeting the requirements from users in that field. Like you say, it’s an experiment that shouldn’t escape the lab.

how do you link to a method in KDoc? what is the equivalent of

#

in javadoc for kdoc?

I think it's just a dot.

[MyClass.foo(String)]

IIRC

Here's a question about best practices... I know that Kotlin does away with the 1 public class per source file requirement that Java has, as well as the requirement than the name of the file match the public class. For an existing Java project that's slowly incorporating Kotlin, what are your thoughts on taking advantage of this (or not)? My particular use case is a set of data classes that comprise an object graph. There's about 4 classes, with about 3 of them being one-liners. It seems odd to use an entire file on a one line class, so I'm tempted to define the entire hierarchy into the same file. But then again I'm anticipating having to defend this decision and I'm finding myself unsure. Thoughts/pointers?

Personally, I prefer the one-class-per file even if Kotlin relaxes the requirement (I'm also working on a project that's transitioning from Java).

@michaelsims: I don’t think there are any rules here. I initially tended to group a lot more classes in one file, since Kotlin makes these much shorter than Java ones, but as my code grows, I realize that being able to locate classes by their file name is useful. For example, to link to them or locate them in github with the magic ’t’ shortcut.

Ah, good point.

i’m with cedric. as I’m building out a particular feature i might put them all in one file but as the code stabilizes and grows, it’s easier to have one class/file.

it’s really easy to have IDEA generate the new class right there in the file but it’s not long before i move it out.

Just to clarify, when Justin says he’s with me, he means in a totally platonic way.

Maybe the ability to do that is more useful if you were using Kotlin for a quick "script"/command line utility, etc.

lol

pines away

@irus thanks a ton. This group looks great! simple smile

@pfn , is it possible in scala to override for example a

Vec2

addition such as

a = b + c

in order to avoid any temporary garbage and save directly the result in

a

?

how do you mean? b + c would generate a new vec and it would be stored in a

is it possible to avoid to instantiate a new vec and store the result directly in

a

?

but then why wouldn't you just say b += c

since that's effectively what you want

because you already have

a

and don't want to modify

b

a += b; a += c

let's suppose then to have a = b / c