Are there any tips on how to speed up the ide? It always takes multiple seconds till the analysis etc. is gone and an import is suggested

Can anyone say if there have been any significant advancements in Kotlin/WASM tooling since the publication of this article, little over a year ago? https://superkotlin.com/kotlin-and-webassembly/ I'm a surprised at the apparent silence on this front; since the push towards WebAssembly (read: away from JavaScript) is one of the most exciting frontiers in mainstream technology at the moment - and with a lot of reward up for grabs. I would not be at all surprised if JetBrains have a dedicated WebAssembly IDE (perhaps as a major iteration of WebStorm) quietly in the works. Posted in #webassembly

Hi! I have experimented with the compiler plugin API a couple of weekends ago, and created DI prototype based on some Dagger concepts (that's the most familiar compile-time DI for me). I am planning to continue developing it further, so it would be great to get some general feedback on the idea and execution. The repo is here: https://github.com/ShikaSD/kotlin-compiler-di The idea I have for further experiments is that with compiler plugin we are no longer limited with annotation processing, so the API can be much more fluent/accessible and richer feature-wise. Thread in #compiler

🔥 🔥 🔥 Give your opinion on what Kotlin-specific extensions or utilities should be added to jOOQ! https://github.com/jOOQ/jOOQ/issues/6256

also, how to do that override a method when instantiate a class to an object in kotlin?

I'm new to Gradle (5.5.1) and Kotlin (1.3.41), using the kotlin-gradle-dsl plugin. Following the documentation at https://docs.gradle.org/current/userguide/java_testing.html#test_reporting, I set up

build.gradle.kts

to aggregate the test reports. The issue is that one of my modules, an API module, doesn't contain tests, and I'm getting this error when I attempt to build: `Task with name 'test' not found in project ':api'. I'm assuming I need to somehow skip that subproject, but I don't exactly know how.

https://twitter.com/kotlin/status/1151902212202721280 To everyone who has helped make Kotlin the success it is today, thank you and have a nice Kotlin! 🙂 https://t.co/YPqTidGTD0 Twitter Next up for the Breakout Project of the Year - congratulations go to @kotlin! #OSCON Twitter

Kotlin wins Breakout Project of the Year award at OSCON ’19 Today at the O’Reilly Open Source Awards 2019, we were honored to hear that Kotlin has won the prestigious Breakout Project of the Year award, this award recognizes a project that has started “breaking out in a big way” over … Continue reading →

and why java and kotlin doesn't support [] operator and {} operator for list and dict aka map???

better than a+= xxx and {"xxx" to "xxx}

just replaced a ton of java code with

.groupingBy { it.statusCd }
.eachCount()

I love kotlin.

Sanity check: This is reasonable in a test case yes?

val zdt = ZonedDateTime.parse("2019-07-19T14:19:05-05:00") ?: fail("Unparseable ZonedDateTime in test code")

what this type as itself’s type variable mean? ‘’’ fun <T> Interable<Iterable<T>>.flatten() : List<T> ‘’’

hi all

hello

Because of the island near Saint-Petersburg: https://en.wikipedia.org/wiki/Kotlin_Island

So like Java island

Would you define an exception as a object?

What is the purpose of DefaultConstructorMaker? Why a sealed class is converted to an abstract class with a synthetic constructor accepting DefaultConstructorMaker as an argument? Isn't the default constructer enough?

What's the benefit of using

lateinit

keyword when one could just assign a null to an object and force NPE using !! operator? If

lateinit

object is not initialized, it will throw exception just the way null object would throw NPE. I don't understand what's the real benefit of using

lateinit

keyword beside not having perform null checks either using safe calls or double bang operators?

that's pretty much it

it allows you to make a constant value that isn't set at object creation time

and continue to treat it as a constant value

If we talk about writing 'safe' code, don't you think that using

lateinit

is not safe because the compiler does not warns if the object is initialized or not. But in the case of null accepting objects, the compiler forces you to take action to prevent NPE? Pretty one sided question, but curious

Yeah, it's just convenience. In some ways its the same as

!!

, as it indicates that the compiler doesn't know if it's not null, but we know that it's not null.

I've used it in circumstances where, due to a library, I am unable to use the constructor to properly ensure not-null

A good example is Android, where you can't use a constructor for an

Activity

, but the first thing you do when the object gets its

onCreate()

callback is set up those variables.

Okay

Or when using a dependency injection library, e.g.

@Inject lateinit var myRepository: MyRepo

.