Conversation

Notices

1. Embed this notice
   pistolero (p@fsebugoutzone.org)'s status on Thursday, 21-Nov-2024 14:55:39 JST pistolero

   • Haelwenn /элвэн/ :triskell:
   • NonPlayableClown
   • ins0mniak
   • 夜化
   @NonPlayableClown @ins0mniak @Yoruka @lanodan There were some kind of baffling rules, Dijkstra's fault. Single-return was probably the most pernicious. They seem to stick around in some of these professors' heads.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 21-Nov-2024 14:55:39 JST Haelwenn /элвэн/ :triskell:

     in reply to

     • NonPlayableClown
     • ins0mniak
     • 夜化
     @p @Yoruka @ins0mniak @NonPlayableClown Single return?
     Damn, I love early returns, in fact it's the one shit I horribly miss whenever I come back to Elixir.
   • Embed this notice
     pistolero (p@fsebugoutzone.org)'s status on Thursday, 21-Nov-2024 15:26:29 JST pistolero

     in reply to

     • Haelwenn /элвэн/ :triskell:
     • NonPlayableClown
     • ins0mniak
     • 夜化
     @lanodan @NonPlayableClown @Yoruka @ins0mniak Yeah, it was alleged that this would make control flow easier and functions more legible, but this is not remotely true. Pascal enforces it, if I recall correctly, or it at least used to. I don't know how they were convinced by the reasoning; guard clauses let you narrow the number of cases under consideration as you walk down the function, obviously easier to read and write.
     Haelwenn /элвэн/ :triskell: likes this.