You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
I think there's general agreement among us four that JSON is not what we want to use. I know that @freeformz and I both lean TOML. But we're gonna have to do this, and probably sooner rather than later.
Unfortunately, there's a wrinkle: one of the major arguments for using YAML or TOML over JSON is that both of those formats support comments, and JSON does not. However, neither BurntSushi/toml nor go-yaml/yaml appear to support encoding comments. idk about other implementations, but...well, that really sucks. (This knowledge courtesy of the cockroachdb folks, reporting it about glide: Masterminds/glide#691)
I don't know where that leaves us, but the clock is ticking.
The text was updated successfully, but these errors were encountered:
so, I feel like the thing to do about this is...once we open up this repo, we basically put out a note saying, "hey, if some awesome Gopher wants to get support for proper comment handling into one of these encoding libs by X date, then we'll use it. otherwise, we'll have to stick with JSON"
I think there's general agreement among us four that JSON is not what we want to use. I know that @freeformz and I both lean TOML. But we're gonna have to do this, and probably sooner rather than later.
Unfortunately, there's a wrinkle: one of the major arguments for using YAML or TOML over JSON is that both of those formats support comments, and JSON does not. However, neither
BurntSushi/toml
norgo-yaml/yaml
appear to support encoding comments. idk about other implementations, but...well, that really sucks. (This knowledge courtesy of the cockroachdb folks, reporting it about glide: Masterminds/glide#691)I don't know where that leaves us, but the clock is ticking.
The text was updated successfully, but these errors were encountered: