Encoder reorders elements, causing incorrect encoding.

[aarondl]

Expected: toml package to encode data properly.
Actual: During encoding it seems like arrays of maps are given some sort of priority, the ordering of the fields is mixed up, and an incorrect toml representation of the object is output.

Given the following reproduce code:

package main

import (
    "bytes"
    "fmt"

    "github.com/BurntSushi/toml"
)

// The object we are trying to build.
var config = `
[map]
zero = 5
[[map.maparr]]
friend = 5
`

func main() {
    var toEncode = map[string]interface{}{
        "map": map[string]interface{}{
            "zero": 5,
            "maparr": []map[string]interface{}{
                map[string]interface{}{
                    "friend": 5,
                },
            },
        },
    }

    b := &bytes.Buffer{}
    enc := toml.NewEncoder(b)
    if err := enc.Encode(toEncode); err != nil {
        fmt.Println("Error encoding:", err)
        return
    }

    fmt.Println(b.String())
}

The expected output of this is:

[map]
  zero = 5
  [[map.maparr]]
    friend = 5

But the actual output is:

[map]

  [[map.maparr]]
    friend = 5
  zero = 5

Because of the ordering of the fields, the field "zero" belongs to the [[map.maparr]] entry rather to the [map] entry, meaning that the encoded toml is incorrect.

[BurntSushi]

Yikes. Reproduced. Working on a fix.

[BurntSushi]

All set. I included your code as a regression test. Thank you!

[aarondl]

Thank you for the prompt fix. You're doing an excellent job maintaining this library :)

[BurntSushi]

Thanks! :)