...but why has that been removed? Looks useful to me.
k
karelpeeters
12/09/2018, 9:09 PM
Because it becomes easier to accidentally change the return type of a function.
o
orangy
12/09/2018, 9:34 PM
You might just want to share a video. There were never such inference in Kotlin, so I wonder if there is just some misunderstanding, or just plain bad video.
👍 2
f
febs
12/10/2018, 5:58 AM
Unfortunately it's copyrighted. This is it: http://shop.oreilly.com/product/0636920052982.do
I think it's bad, too. It also makes another mistake when tries to show a loop:
for ( i in 10 .. 1)
which doesn't work.
This is quite absurd considering it comes from a Kotlin author but that's it.
h
hhariri
12/10/2018, 6:28 AM
Those were mistakes. I have no idea now why I made them, but I'll reach out to O'Reilly to see if we can have it highlighted somehow. Apologies.
hhariri
12/10/2018, 6:29 AM
If you can send me the exact video title and minute that would be useful. Thanks