Glob specification is not clear

[Conaclos]

This is related to #45.

When reading the Glob Expression section of the specification, I have several questions unanswered:

1. Are globs unicode-aware? Globs from .gitIgnore are not unicode-aware. This means that the globs [é] and ? don't match é.
2. How is handled three or more stars ***? Usually glob libraries treat it as a single star, or as an invalid glob expression.
3. Can character class match against /? Usually glob libraries don't allow that.
4. Can {s1,s2,s3} contain nested glob expressions? e.g. {*.json,*.toml}.
5. Can {s1,s2,s3} contain empty strings? e.g. {*.gen,}.json.
6. Does {num1..num2} allow reversed ranges such as {1..0}?
7. Does {num1..num2} allow numbers with leading zeros such as {01..02} If yes, is this equivalent to [12] or 0[12]?
8. Does {num1..num2} allow numbers with a + sign? e.g. {+1..2}?

Thanks!

[florianb]

@Conaclos thanks for bringing this to our attention. I think the specification is unclear at that point because I'm fact two separate technologies seem to apply: glob and brace expansion.

I need to do further research on that topic.

[Conaclos]

Feel free to tag me if you need a review or some help.