When you use

with

, do you add a space after it so it looks like control flow? 1️⃣

with (context) {
  foo()
  bar = 42
}

2️⃣

with(context) {
  foo()
  bar = 42
}

1️⃣

open class BaseResponse {
    val isSuccess: Boolean
        get() = errorCode == 0
}

2️⃣

open class BaseResponse {    
    fun isSuccess() = errorCode == 0
}

Ran across this https://www.reddit.com/r/programming/comments/6isguk/kotlin_heavyweight_language_or_hopeless_hype/

Am I missing something? Does

gojf

work with Kotlin too or what?

half a day on a shitty bug because of deg instead rad.. can wait to have inline classes

guess I should have made this a thread.. yeah I had a 2017 for 4 or 5 months this year, maybe adjusted brightness with it once or twice..

you mean you don’t run Slack?

@orangy I have the same rMBP top of the line, but I’m still a Scala guy at work… so my current project takes 26 minutes to compile and the fans on this baby sound like they’re about to take off

If you run Android studio with an emulator, the fans are always on 😂

on that MBP topic

It was mentioned (https://kotlinlang.slack.com/archives/C3SGXARS6/p1532054420000064) that Swift and Rust are supported (but not Kotlin) on Fuchsia, where does this information come from?

I see Rust here: https://github.com/fuchsia-mirror/docs/blob/master/development/README.md#languages

How to fix dependencies in python: reinstall the whole thing

What's the point of inner class when value type are going to be implemented soon ?

@sksk Why do you think that value types are close? Looks like even general architecture of value types on Java is still under consideration. And value types that are not compatible with Java-ones is bad idea in terms of future interop “inner class”? Do you mean “Inline classes”? They allow to solve some use cases right now and even for old JVMs and Android, because it’s just a compiler feature

just have structs instead

So actually value types, or I miss some key difference? It’s also bad idea to introduce potentially incompatible implementation of value types only for Native, because when value types will be available on JVM you want to have the same API as native

An Idea for a T-Shirt: ⌘⌥⇧K WDYT? 😄

Not sure where to post this, but the reference page on properties and fields has incorrect indentation in second and third codeblocks under Getters and Setters (https://kotlinlang.org/docs/reference/properties.html#getters-and-setters), which might be confusing for a beginner.

was kinda curious on how unit tests were written for

apply

,

with

, etc. couldn't find it on the public repo. does anyone know about it?

hey guys, I have a mock server https://mocklets.com which helps in simulating HTTP-based APIs for front end development. Currently we are providing only cloud-based service, but from the feedback we received from our users, there is also a need of hosted services which can be deployed on in-house infrastructure for the clients who don't want to expose their API schema to the cloud. So we are looking to develop a variant of our service to be hosted on client's infrastructure. Since the service will be using a database to store information, we are struggling on how to setup a database along with the setup process, and also don't want to expose our database schema to our client. Can anyone guide me towards any solution? Thanks

so, playing around with inline class, I'm exploring their usage for enums (regarding c/c++ binding/port libs). Inline enums are not yet available, however I'm somehow not complaining about this inside ^^. From some early experience, I can tell you I seem to like more inline classes than inline enums because you can simply

inline class DrawMode(val i: Int)
val Triangles = DrawMode(GL_TRIANGLES)
...
fun glDrawArray(mode: DrawMode, count: Int) = ..

whenever I type `glDrawArray(`and I call for type completition all

DrawMode

top level members will be available and suggested as first ones. I like this because I don't have to type

glDrawArray(DrawMode.Triangles, ..)

. I know I can work on the import, but this is overhead for me. Disadvantage, final user can of course implement it's own/additional

DrawMode

(not really a vs, since this gives the possibility for the user to add some newer enums from the latest API, where I still didnt catch on) and they are not guaranteed to be unique. Do you see other differences? What's your feeling about this? I'm looking especially at you @gildor @karelpeeters @louiscad @diesieben07 🙂

When did Jetbrains have an event in Tel Aviv?

https://twitter.com/jiriknesl/status/1021814817592496128 — isn't that what arrow is for?

Hey guys, when developing chats, do people roll their own websocket and stuff or is there go-to library? Im new to the domain

3.1.7

Set Tab Title

Does

kotlinlang.slack

team now has full history?

Hey, need a few people that know Java at least a little (bad is fine, good is ok too!) to do a quick 5-6 minute experiment. It is a tiny coding problem that just needs to see some alternative variations. message me if you have <= 10 minutes to burn.

finally, I cant wait! https://github.com/Kotlin/KEEP/issues/142