TOML versions `1.1` and `latest` don't behave the same

[Akuli]

TOML 1.1 added \x escapes. For example, https://toml.io/en/v1.1.0 shows the following example. Note the \xE9.

str = "I'm a string. \"You can quote me\". Name\tJos\xE9\nLocation\tSF."

The file invalid/string/basic-byte-escapes contains answer = "\x33", which seems like a valid \x escape to me. So I was wondering why toml-test expected my parser to emit an error. Turns out I need to specify -toml 1.1, and the default -toml latest won't work:

akuli@Akuli-ThinkPad:~/jou/toml$ ./toml-test-v2.1.0-linux-amd64 list -toml 1.1 | grep basic-byte
akuli@Akuli-ThinkPad:~/jou/toml$ ./toml-test-v2.1.0-linux-amd64 list -toml latest | grep basic-byte
invalid/string/basic-byte-escapes.toml
akuli@Akuli-ThinkPad:~/jou/toml$ 

Are 1.1 and latest supposed to be equivalent? I guessed so from the available choices (1.0, 1.1, latest) but that seems to be wrong.

[arp242]

Looks like I forgot to update the DefaultVersion here: https://github.com/toml-lang/toml-test/blob/main/runner.go#L34

So yeah, latest refers to 1.0 instead of 1.1.

I guess no one is using it because no one else reported it? Maybe I should just remove the latest alias? 🤔

[ChristianSi]

latest alias still seems useful, I'd keep it! People rarely report bugs, even if they run into them.