So, I had a discussion with my colleague about null safety and how it can be non-intuitive if you're not yet used to it.
So we had the following code:
In a lot of REST applications, an Exception may be thrown when a resource does not exist. But it's important to differentiate between "no resource" and "oh no! An exception occurred! We're in trouble!".
That's what this example code does.
So, what did the "getStatus" method do exactly?
This causes the test to fail.
The code should have been "?: false", but doing that does look weird.
A clearer solution would be:
The problem with Kotlin might be that there's alot of "?." and "?:" and "!!" and quite frankly it makes it hard to read.
What do you think?
No comments:
Post a Comment