In the previous episode, we looked at parsing a log file. We initially used data classes to represent the different types of events that we saw, but found that they could be clumsy when representing type hierarchies, and we had to fall back on reflection in order to select properties specified by strings.
In contrast using maps to represent the data was (in this instance) less awkward, and they made it easy to select properties by name....
I’ve been listening to an (and another) excellent podcast by Clojure programmers recently and learned that nobody builds classes in Clojure; and certainly not to represent data. Instead they populate maps for all the uses where Kotlin developers would reach for a data class.
I’ve got very used to data classes and like them a lot, but there are certainly situations in which they don’t shine. Today I’m going to look using maps instead.
Let’s...
Nat Pryce and I have been asked to run our popular Refactoring to Kotlin Workshop at KotlinConf 2019 in Copenhagen.
If you are attending the conference but relatively new to the language it is an excellent way to get up to speed on the language and its idioms.
This is Part 7 in a series looking at functional error handling in Kotlin. The parts are
Today I’d like to talk about avoiding error handling.
If...
This is Part 6 in a series looking at functional error handling in Kotlin. The parts are
It has been over a year since I wrote Part...