# yeah, i don't mean to critique your application logic; i generally assume that
# you do what you have to do. but stylistically speaking, i consider a construct
# like the code snippet in your original question to be akin to how, for example,
# in a language that didn't have case expressions you might write something like
let x: int
case y
of 0: x = 1
else: x = 2
# instead of
let x =
  case y
  of 0: 1
  else: 2
# i.e., that it conceptually represents a single operation separately from its
# specific realization in the language