Practical Go: Real-world advice for writing maintainable Go programs

Re:Practical Go: Real-world advice for writing maintainable ... by jerf on Thursday February 21, 2019 @12:54PM (#19218896)

The authors have chosen to make it as limited as they have on purpose, as I understand it.

I disagree with them, but here we are.

I've been slightly tempted at times to make something with markdown but never gotten enthusiastic enough to put the time. Plus, markdown is technically a bit too powerful, so I'd want to cut it back down, and before you know it I'm inflicting the 3,124th custom markdown on the world. Really I just would like bold, italic, monospace, identifier linking as you say, and numbered and bulleted lists not in the unformatted text wrapper.

[ Parent | on HN ]

Re:Practical Go: Real-world advice for writing maintainable ... by noir_lord on Thursday February 21, 2019 @02:55PM (#19220013)

I'd just like to be able to toggle javadoc, phpdoc, godoc visibility on and off entirely (not collapsed to a line, or a marker) just make them vanish until I summon them back.

I find them distracting when I'm reading the code but I don't want them not to exist either.

EDIT: Another thing I'd love to be able to do is 'tag' a variable with a synonym and have that appear next to it eveywhere.

so $strCstAcctRec (I wish that was fake but it's pretty much straight out the codebase I inherited..) would show up as $strCstAcctRec (CustomerAccountRecord).

There are a bunch of ergonomic features like that I've considered over the years, I might at some point try implementing some of them as an intellij plugin.

[ Parent | on HN ]

Re:Practical Go: Real-world advice for writing maintainable ... by Gibbon1 on Saturday February 23, 2019 @04:18AM (#19232487)

I've used an IDE that was aware of doxygen comments. Seems like that's close to what you want. You could right click and it'd show you the comment. I loved that IDE and it's long gone.

[ Parent | on HN ]