re: The case for multiline signatures VIEW POST

VIEW FULL DISCUSSION

I'm personally a fan of not using multiline signatures as they clutter a lot. However, this is only a thing when using interfaces. When using interfaces, you won't (often) change the signature either way.

When not using interfaces (like constructors or callables), it's a good idea to take a step back and wonder if you really need that many arguments. If you do, multiline. If you don't > refactor.

I think it should be completely okay to "clutter" an interface with signatures, because you are definitely not supposed to have many methods in an interface, see the ISP. Plus, even if you don't change them often, they should still be easy to read too, especially in the Github editor.

I didn't make this clear in my post, sorry about that.

Talking about interfaces, I mean the implementations thereof, not that actual interface. The signature in the interface is something important, whereas the implementation I couldn't care less about.

code of conduct - report abuse