> Don't do relative imports (littlelang/tokenizer) or . littlelang/tokenizer > . Unless you want to run into corner cases with tools not knowing where > code is defined or if you want to confuse other developers. > > Using the full path makes it very clear where the code is, yes, if you > move things around.refactor you may have to edit the path, but in Go it's > not about saving the writer of code time, it's about saving all the readers > of code time (including yourself in a year). >
Aha, I just figured this out based on Matt's message -- thanks! > That's the only big thing I noticed on your project, the rest looks good. > One minor thing may be that instead of using os.Args, I would use the > flag's package. > Good call. -Ben -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
