3 ms·
I find both the golang uppercase lowercase naming scheme and python underscores for private (and __ for *extra* private) to be terrible design choices. They ar
by callc 1y ago
I find both the golang uppercase lowercase naming scheme and python underscores for private (and __ for *extra* private) to be terrible design choices.
They are hidden functionality, a set of rules which must be remembered. “Make sure to do <weird trick> because that mean <X> in <PL>”
Leave identifier names alone. Packing extra info inside is unnecessary mental burden
- arccy 1y agothe other option seems worse, i dunno if i can use this identifier unless i have an IDE or i look up the definition every time
- mdaniel 1y agoAlso, I recently learned that only leading __ are considered special, whereas both sets of __ go back to being a public method due to the dunder magic methods such as __add__, __eq__, etc
- callc 1y agoOh yeah, I didn’t even notice. Much worse than I thought! Imagine explaining these rules to a beginner learning programming.
- Doxin 1y agoIt should be mentioned that within the python community using __ for extra private is widely seen as a misfeature that shouldn't've been added and shouldn't be used.
- masklinn 1y ago> and __ for extra private That was never its purpose and using it that way is in fact misuse. Name mangling was added to avoid unintentional conflicts in inheritance scenarios. That’s why it’s static, simple, and well documented.