Joined May 2013
·
Posted to
Dealing with Unicode in Go
over 1 year
ago
@cthom06 Yeah, you're right, even the utf8 package itself is like a very thin abstraction layer for using strings as []rune. Putting Unicode in strings and assuming the best is an easy pitfall though, one that took me, being new to Go, slightly by surprise!
Achievements
948 Karma
648,535 Total ProTip Views
Bear
Have at least one original repo where Objective-C is the dominant language
Altruist
Increase developer well-being by sharing at least 20 open source projects
Lemmings 100
Write something great enough to have at least 100 watchers of the project
Forked 20
Have an established project that's been forked at least 20 times
T-Rex
Have at least one original repo where C is the dominant language
Beaver 3
Have at least three original repo where go is the dominant language
Python 3
Have at least three original repos where Python is the dominant language
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Beaver
Have at least one original repo where go is the dominant language
Forked
Have a project valued enough to be forked by someone else
Charity
Fork and commit to someone's open source project in need
Python
Would you expect anything less? Have at least one original repo where Python is the dominant language
Cub
Have at least one original jQuery or Prototype open source repo
@unnali I wanted to leave the impression that you can never be too sure what you're going to get in a string, so I'm glad to hear it was unsettling :)