Thank you compose team I didn t laugh that much while develo

Question

Thank you compose team I didn t laugh that much while developing for a while now joy And yes I just finished Queens Gambit on Netflix see no evil

ian.shaun.thomas · Answer

ship it

Big Chungus · Answer

Is it intentionally so buggy

Paul Woitaschek · Answer

Isn t this how chess is supposed to work

Ole K. Øverland (Norway) · Answer

Chess 2 0

marstran · Answer

Is this the off by 1 opening

Paul Woitaschek · Answer

It s the cut out pieces of the board with a saw opening

xetra11 · Answer

it should be called Chonk

xetra11 · Answer

< Paul Woitaschek> also how dare you to do this in kotlin

Paul Woitaschek · Answer

What s wrong with that

Michal Harakal · Answer

```removed let ``` < xetra11>

xetra11 · Answer

ye do the let stuff with fancy kotlin nullables

xetra11 · Answer

its magic < Paul Woitaschek> please join the magical side

Paul Woitaschek · Answer

Nah the code is fine like it is

Paul Woitaschek · Answer

Its easy to read and makes use of smart casts

Big Chungus · Answer

I m with < Paul Woitaschek> on this one Let can be easily abused

xetra11 · Answer

< Big Chungus> Do you have an example at hand

Big Chungus · Answer

Not at hand but too many nested let push the code too far to the right and can make it hard to follow All I m saying is that java style null checks are nothing to be affraid of While they are a bit more verbose I feel they make the code easier to follow

xetra11 · Answer

Hm wouldn t the amount of nested if x = null be the same as the ones of nested lets

xetra11 · Answer

It took me a while to feel let like I felt if x = null that I have to admit But after I became warm with ` ` and the whole things I really feel it s nicer Just my opinion tho

Big Chungus · Answer

Yes but you can do multiple null checks in java style check

xetra11 · Answer

Well ok that is possible but I don t design code like that so I think we have different styles smile luckily there is something for everybody 0

Paul Woitaschek · Answer

I only use let for scoping when the body of the function becomes so complex that the scoping is actually helpful But in most cases that applies I d refactor the function into smaller functions before doing that Regular if checks make use of smart casts and whats nice of these is that multiple smart casts work together

Paul Woitaschek · Answer

This ```if currency = null amp amp rate = null result currency = rate ``` Is easier to understand than this ```currency let rate let rate gt result it = rate ```

xetra11 · Answer

Well I have to admit that this is true However as I mentioned I rarely come over code sections where I need to check two things for `null` since I strip them to be not null as early as possible In my projects nullable data is mostly coming from perstistence or filesystem layers and I strip them to notnull as soon as I read query the data Afterwards I never have to care about null states again

gildor · Answer

if null check is almost always better than using let for null check