News for hackers. Stuff that matters.

A comment on Practical Go: Real-world advice for writing maintainable Go programs. Parent comment

Re:Practical Go: Real-world advice for writing maintainable ... by bnolsen on Thursday February 21, 2019 @10:32PM (#19222878)
no, it's not. bigger deal is that single letter vars make it much harder to search for variable usage in files using arbitrary editors.
[ Parent | on HN ]
Re:Practical Go: Real-world advice for writing maintainable ... by coldtea on Friday February 22, 2019 @12:37AM (#19223380)
Don't use arbitrary editors, or editors that don't support "search for standalone identifier" (e.g. surrounded by space, in (), with ; after etc.".
[ Parent | on HN ]
Re:Practical Go: Real-world advice for writing maintainable ... by apoorvgarg on Thursday February 21, 2019 @11:36PM (#19223163)
What would be the signature of your gcd function ?
[ Parent | on HN ]
Re:Practical Go: Real-world advice for writing maintainable ... by base698 on Thursday February 21, 2019 @11:59PM (#19223259)
Numerator, denominator?
[ Parent | on HN ]
Re:Practical Go: Real-world advice for writing maintainable ... by mrgriffin on Friday February 22, 2019 @04:54AM (#19224203)
For GCD? I would find those names very misleading since semantically the order of the arguments to GCD is irrelevant (even if in the implementation you typically mod by b there's no reason you couldn't mod by a).
[ Parent | on HN ]
Re:Practical Go: Real-world advice for writing maintainable ... by sacado2 on Friday February 22, 2019 @05:36AM (#19224351)
This is not mathematically correct. Those names would be pretty misleading, actually.
[ Parent | on HN ]
Re:Practical Go: Real-world advice for writing maintainable ... by coldtea on Friday February 22, 2019 @12:37AM (#19223384)
Good luck with any bigger equation then
[ Parent | on HN ]