Hacker News new | past | comments | ask | show | jobs | submit login

It is niche, but it does come up. Usually with boolean parameters, but also on migrations. Makes it possible to change defaults in a controlled way rather easily, since you can very easily log all of the places you used the default.



Nah, you should be using another value if you care about that. For example in C# a nullable bool would be a fine choice (three values: true, false, null), or alternatively Option types.


This feels like classic blaming the user. :)

You can also have better behavior between multiple defaults if you know whether someone gave a value or not.

Basically, it is another tool compared to overloading. It should be no surprise that there can be preference on how to use between them.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: