Migrated WordGap from Python to Go 1

Re:Migrated WordGap from Python to Go 1 by georgemcbay on Saturday March 23, 2013 @10:03PM (#5430748)

You can do a sorta-like getattr in Go using reflect, though I'm not sure exactly what your use case is. Fields need to be exported (upper-case names) though:

http://play.golang.org/p/XPgHkKCz_D

But you're absolutely right, you trade in some easy expressiveness and lack of boilerplate for better performance and easy concurrency.

But Go is much better about the boilerplate required than most other static/compiled languages, IMO.

[ Parent | on HN ]

Re:Migrated WordGap from Python to Go 1 by waterside81 on Saturday March 23, 2013 @10:38PM (#5430839)

I like your solution but that's kind of the rub about Go, at least at this stage of its still-early life. You have to re-invent the wheel a lot. It's frustrating to have to implement things that you know exist elsewhere, especially things like collections.defaultdict in Python.

Agree re: boilerplate. Much slimmer than Java or C++. And the build times, my God, the build times. It almost makes up for not having a true REPL.

[ Parent | on HN ]