2 ms·
as somebody who has written a lot of java and kotlin, often I prefer the most explicit option. Code will be mostly read, not written, so if something will make
by on_and_off 6y ago
as somebody who has written a lot of java and kotlin, often I prefer the most explicit option.
Code will be mostly read, not written, so if something will make a junior (or in some cases even seasoned) dev scratch their head to be understood, it is best avoided.
EG Often I prefer writing an "if != null else" instead of chaining takeIf{}s.