What I'm missing:

1. The readme doesn't make it clear what its "float" type is. A double, a decimal, implementation defined. I'm generally not a fan of restricting numbers to what a double can represent, like toml does.

2. It doesn't have a good way to model key-value pair like types such as tagged unions, polymorphic types, or function invocations. Simply allowing a key-value pair as a value (right associative) where the key is a string matching the keys of an object would fix this. Alternatively a function call syntax would fix this, which would also enable tuples as a concept distinct from arrays.

Looks like Windows *.ini format except ":" instead of "="...

Not really. INI has a fixed structure (section>key>value) and its values are untyped.

So a stripped down variant of cue? Why not use cue directly?

Cue only really exists in go, and has a dependency chain to make maven weep.

I think cue is better thought of as a language you use to generate JSON (or yaml, or, let's be honest, k8s flavored yaml) configs rather than a config language you use in your app.

Can you add README sections for the schema and supported types?

See also: HUML [1]

1: https://huml.io/

> Top-level arrays. A TOML file is always a table, so a list of records needs a wrapper key.

I'm curious for example configs that are top-level lists?