Pasted image at 2016_03_07 11_24 PM.png

yeah, i’m still learning to decipher all those, too

I think the white icon means “multiple classes in this file”. “C” means the class name and file name match, but unsure about the color difference

Regardless of what they mean, I don’t think there’s much value in using these different icons so I’d rather have just one

I discovered yesterday that in Kotlin you have to remember to rename the class if you rename the file.. something I'm not really used to

@Dalinar: Not always true in my experience, but I agree it doesn’t seem to always rename both

I’m guessing it would only do that for round icons but not white ones (?)

I only put multiple classes into a single file if they are very short, for example a few data classes that are related to each other. In most cases I use seperate files though.

@michaelsims: objec graph is an ideal situation for grouping data classes in one file. If these classes represent nodes, they hardly have any significant behaviour, so no code pollution in this case

FWIW, I hated #SBT but then after using it for a while, appreciated at least what it was trying to do (that so many other crap tools had either punted on or minimized). After a decade and a half in Java, our choices were Ant and Maven and the Maven plugins for eclipse and even IJ were garbage. They finally fixed the eclipse one, but in so doing, also made it so that rerunning unit tests often triggered a full build, which was so moronic it made my head hurt. (No wonder so many people think TDD sucks…) @cedric is right though: the DSL was stupid beyond belief. Whitespace should not be part of your syntactic plan. I took that as a symptom of utter myopia. They all knew it did that. And never cared to gauge what the OOBE was.

Want to use Scala on Android, knock yourself out. But saying it’s fine to do so is… facepalmy

it's fine to do so, no matter how hard you argue otherwise (and many are using it professionally)

Which one of you is running daily kotlin Twitter? :P

@pfn What does scala give you that you can't get else where

the type system

Nebulous answer is nebulous

ceylon's type system is approaching it, and exceeds in some aspects

but not enough to make me switch to ceylon which would have "official" android support

What specifically do you use in Scala's type system that say Kotlin can't provide

I already said previously, higher kinded and path dependent types

I wasn't here earlier

slack keeps a scroll buffer 😛

No offence I am not going to go digging into past conversation to find out what your personal gripe is. So why are you in #random in kotlin-lang?

because it's #random

I mean if you are so set using Scala. Why bother?

because I maintain a few tools to support kotlin users

(few = 1)

@code-crusher me

@irus great. We are setting up a Kotlin User group in New Delhi, IN. It would be great to connect to you for assistance :) Also it would be great if other kotlin devs can help 😄

@code-crusher okay, if you need retweets or whatever i will help you 🙂 Personally i support Belarus Kotlin User Group https://bkug.by 🙂