Thanks, Ingo! Finding the names of things in the stdlib is always half the battle in learning to do useful things in a new language. I'm surprised my Google searches didn't turn those up. Anyway, ParseInt and FormatInt and kin are now my new best friends.
Prior to trying pytogo, my strategy was to rewrite a central piece of the app that talks to all the other processes and then port the Python processes one at a time as goroutines. That's working very well so far. It's using less CPU and RAM and seems more stable. As I replied to Eric, pytogo seems like it might speed up the process of porting other pieces of the app by providing a good first draft. On Wednesday, October 3, 2018 at 2:57:49 PM UTC-4, Ingo Oeser wrote: > > Hi Michael, > > while I understand that you are having fun with the pytogo translator, > please note that a base36 encoder is already part of the Go stdlib > > Namely https://golang.org/pkg/math/big/#Int.Text supports a base of 36 > for big integers and https://golang.org/pkg/strconv/#FormatInt supports > base 36 as well. > > Maybe this helps reducing the python code you need to convert as well as > speed up the result by accident. > > Have fun! > > -- 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.
