TOML Include

[harrymkt]

This TOML include still has no support for backslash escapes, of course

[Lucas18503]

How does this meaningfully differ from the existing ini include? As ini and TOML are so similar, I think that would be useful to know.

[harrymkt]

@Lucas18503

They are similar, but no in many areas. A few examples:

INI:

test=Hello there

Goes to TOML

test = "Hello there"

Notice using quotes.

Also, this has a very reliable indentation support for subsections compared to INI include.

Because some may want to use because some API uses TOML.

The current downsides are:

1. It needs tables, and lists support, including inline lists.
2. Backslash escape support is needed.

The reason I've created this was because the API I used to fetch the data isn't useful with the INI include, so I created for myself. But then I've decided that just like me, NVGT community might need it so I've just made a pull request.

Of course, this current version and INI isn't that much different; However future features of TOML would make both the differents, including inline lists and inline tables.

player = [
	{name = "Jon", feet = 5.6},
	{name = "Alex", feet = 5.4}
]

That's just a table with inline lists.

The same result but different writing style:

[[players]]
	name = "Jon"
	feet = 5.6
[[players]]
	name = "Alex"
	feet = 5.4

[ethindp]

Are you hoping to have this merged once it's passed the TOML test suite or before?

[harrymkt]

@ethindp I think this PR can be merged even though without inline tables and lists, because we have the properly working basic values that users will be using with. Strings, intagers, floatingpoints, boolians.

[alexoloopios]

This could be useful in the future, but I don't see why we would need this now, but then again I'm a newb so this is new to me.