make style consistent in Hy source

[gilch]

Should there be one blank line or two between top level forms? How many semicolons in comments in which contexts? The style guide in the documentation is silent on some issues. Should the Python "dunder" forms be rendered like --init-- or __init__ in Hy? We're just not being consistent. It varies from file to file, and sometimes within a file. When I make edits I try to be consistent with the file I'm editing, but sometimes this is hard.

The easiest way to keep this consistent given multiple developers is probably with automated style checks. We don't seem to have that set up. Perhaps Hydiomatic is a start? Has anybody tried running Hy's source through that? Can we add it to continuous integration somehow?

[Kodiologist]

This is a pretty deep rabbit hole considering that the language is a moving target (inherently, in its own implementation), that we want to test code that's badly styled, and that idiosyncratic programming is the point of Lisp to begin with. Let's just make sure the code is readable, because style is only for humans; the computer running the code is unaffected. We'll have plenty to keep us busy working on Hy without trying to enforce the use of double spaces between loop clauses in lfor. Also, we've removed a lot of redundant features since this issue was originally posted, so at least it should be more obvious how to do stuff now.