News for hackers. Stuff that matters.
Re:Kotlin 1.4 by The_Colonel on Tuesday August 18, 2020 @09:33AM (#24198315)
> Kotlin will have to choose to either give up on low-overhead abstractions, give up on some of its platforms, give up on giving access to full platform capabilities

It can be just reasonable mix of all of this.

> if Kotlin's inline types will make use of Valhalla, then they won't work on Android, at least not without much overhead.

Looks to me like a valid strategy.

Re:Kotlin 1.4 by pron on Tuesday August 18, 2020 @10:03AM (#24198651)
Oh, I'm sure they'll do something reasonable, but whatever it is, it either significantly scales back the goals or it turns Kotlin from a "there's nothing to lose" proposition to a "there are new tradeoffs and added risks to consider" proposition.
Re:Kotlin 1.4 by thu2111 on Tuesday August 18, 2020 @03:18PM (#24203064)
Assuming Android doesn't support Valhalla at all, I suspect they'll just introduce an Android specific backend in which inline classes with >1 member are compile errors. The language is already slightly different between platform targets anyway so it's no big leap.