serde-yaml 0.5.0 is harder to test because keys are no longer alphabetical about serde-yaml

[dtolnay]

I definitely should have mentioned this in the release notes - added now. The keys will be in the same order as they appear in the struct.

I think this is a better default than sorting everything. Often there is a particular order that makes sense in the source code, and the same order most likely makes sense in YAML too. It also matches the behavior of serde_json as well as the equivalent Go code.

Are you going to need a way to revert to the previous sorting behavior and if so, rather than sorting in serde_yaml how would you feel about a container attribute like #[serde(serialize_sorted)] to sort at compile time?

package main

import (
    "fmt"
    "gopkg.in/yaml.v2"
)

const y = `
"file": "bar/docker-compose.yml"
"service": "foo"
`

type Extends struct {
    Service string
    File    string
}

func main() {
    var data Extends
    err := yaml.Unmarshal([]byte(y), &data)
    if err != nil {
        panic(err)
    }

    y2, err := yaml.Marshal(data)
    if err != nil {
        panic(err)
    }

    // service: foo
    // file: bar/docker-compose.yml
    fmt.Print(string(y2))
}

[emk]

Actually, source order is _great_. As long as the order is consistent from run to run, we can maintain testability and diff-ability. There's definitely no need to support alphabetic order. Thank you very much!