I've done some work on the read_token function.
The implementation on the site has some problems.
* The string conversion to chstr is unnecessary. Rune comparisons can be done simple with `ch == '('`.
* The 128 byte buffer will cause a panic when you enter an atom that exceeds this size. The idiomatic way to do this, is to use a `bytes.Buffer` instance.
* There is also an extra error check in the rune reading loop. The original ignored possible EOF's. Not sure how relevant it was in this particular use case, but just ignoring errors outright is never a good idea.