{"comment":{"url":"https://api.github.com/repos/quinnj/Strings.jl/comments/11660538","html_url":"https://github.com/quinnj/Strings.jl/commit/20e0612da8c958719b9a838b6e0fdf0bf7a1115b#commitcomment-11660538","id":11660538,"user":{"login":"quinnj","id":2896623,"avatar_url":"https://avatars.githubusercontent.com/u/2896623?v=3","gravatar_id":"","url":"https://api.github.com/users/quinnj","html_url":"https://github.com/quinnj","followers_url":"https://api.github.com/users/quinnj/followers","following_url":"https://api.github.com/users/quinnj/following{/other_user}","gists_url":"https://api.github.com/users/quinnj/gists{/gist_id}","starred_url":"https://api.github.com/users/quinnj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/quinnj/subscriptions","organizations_url":"https://api.github.com/users/quinnj/orgs","repos_url":"https://api.github.com/users/quinnj/repos","events_url":"https://api.github.com/users/quinnj/events{/privacy}","received_events_url":"https://api.github.com/users/quinnj/received_events","type":"User","site_admin":false},"position":null,"line":null,"path":"","commit_id":"20e0612da8c958719b9a838b6e0fdf0bf7a1115b","created_at":"2015-06-12T19:31:00Z","updated_at":"2015-06-12T19:31:00Z","body":"Yeah, @ScottPJones, I don't think it's a matter of not understanding *what* `Encodings` are, but *how* we're going to use them exactly. Like I mentioned above, adding them right away would cause a little weirdness because we have `UTF8String`,`UTF16String`,etc. and with `Encodings`, we'd have `UTF8`,`UTF16`,etc. \r\n\r\nLike I said before, this is a much better change to introduce with a larger overhaul where it can be grafted in all the various corners that encodings touch (as opposed to using it just for a `check_string` function)."}}