Using Option too much in your #rustlang function parameters can make your code really difficult to read or modify. So error prone trying to figure out which `None` to change in `foo(3, x, None, None, None, None, None)`.
Conversation
i would go further and suggest that functions should not have more than one optional parameter or more than like, four parameters total
4
1
26
yeah strong agree, though the latter isn't always possible because in rust does not let you arbitrarily subdivide functions, there are things that can exist at the local level that cannot be expressed in function signatures
2
1
10
Arg yeah, this is one of the more frustrating parts of Rust. Non-lexical lifetimes are great, but it definitely goes outside of what you can express in the type system. Really frustrating when you absolutely need an existential lifetime, and have to use a macro instead. 😢