is there already an issue about having a `return` ...
# language-proposals
e
is there already an issue about having a
return
inside a constructor? Because right now I'm forced to use multiple
if-else
with the consequent indentations
r
refactor your constructor to some small private methods
e
I wouldn't like to go down this road, because since it's a port, I'd like to stick as much as possible to the original version to keep maintenance as low as possible
k
Just use a secondary constructor instead. Or a factory method.
e
uhm, I'll see