thomasnield
05/30/2018, 3:58 PMmkobit
05/30/2018, 4:02 PMbaermitumlaut
05/30/2018, 4:02 PMthomasnield
05/30/2018, 4:05 PMdalexander
05/30/2018, 4:17 PMHong
05/30/2018, 4:43 PMthomasnield
05/30/2018, 5:00 PMHamza
05/30/2018, 11:50 PMedwardwongtl
05/31/2018, 3:47 AMvoddan
05/31/2018, 6:36 AMedwardwongtl
05/31/2018, 6:37 AMrawtoast
05/31/2018, 8:13 AMval
,var
,let
, etc. when almost every new language uses local type inference…Hamza
05/31/2018, 10:27 AMdalexander
05/31/2018, 1:00 PMPere Casafont
05/31/2018, 1:33 PMxenoterracide
05/31/2018, 1:34 PMrawtoast
05/31/2018, 1:44 PMPere Casafont
05/31/2018, 1:51 PMva
and the decision of final or variable is just a character 😛xenoterracide
05/31/2018, 2:03 PMvar
to always be final... since most of the time I don't actually have a use case for a local variable to be nonfinal, and if I do... I usually would call that code smell. Reason I'm worried about inference is not all concrete classes are as clean as java's core ones, meaning I think we'll suddenly see methods being used, or seen that wouldn't normally be available if you were assigning to an interface. of all the features they could have chosen to add, this was the weakest one imho. I'd still much rather have had a way to define a property without all the boilerplate...hoang
06/01/2018, 6:57 AMval/var
hard to read in printed kotlin
. Wow, remind me of an old Software competition 10 years ago when we had to print our whole project's source code and submitted that thick book 😄