Hmm... good observation. I'm quite used to using conditionals this way (mostly because i program in Ruby on a daily basis), but i'm not sure it's a very solid practice. In fact, i'm pretty sure that if i were to design a language, i wouldn't allow non-boolean expressions in conditionals; it just adds special corner-cases to the language (like what values are "falsy" and whether that behaviour can be overriden, etc).

In this case, the statements could be rewritten as `code = error.code if error.code?` and they'd be safer. I don't think we're gonna have problems with those because falsy code (i.e. empty strings) should not cause compilation errors, but i wouldn't oppose the change either :wink: