This is a perfectly normal way to end a 65 line procedure, I don't see the problem

In my defense, that means that a huge amount of state was successfully encapsulated and we can now go back to pretending the world is pretty and functional and just do normal applicative programming without any worries.

What that monster returns though, you're in trouble.

@tfb Is it some Lisp dialect? I rarely write functions longer than 20 lines...

@mdallastella Yeah, it's a scheme, working hard to earn Lisp's reputation for too many parens. I don't normally write 60+ line side-efectful monsters like that, which is why those 13 closing parens were so funny to me.

@tfb Besides, for all we know syntactic sugar might cause diabetes.

@tfb why would there be? It could be worse, it could be the same number of characters, but they could be } and be one on each line with the different indentation. That would be awful. Lucky no languages force you to go through that.

@loke Oh I'm not complaining about parens in general, I'm more amused at how the ugliness if the whole procedure shows through in its final line.

Ok, and typing close paren 13 times in a row was kind of annoying too. I normally do balanced editing, but I'd blown away and rewritten the end of that form.

@tfb Yeah, my post was just a comment on how apparently )))) is unacceptable while:


Is very nice apparently.

@loke Oh you haven't seen the dominant style in microelectronics, I bet:

) ; end if
) ; end let
) ; end when
) ; end prog
Sign in to participate in the conversation
Functional Café

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!