Windows-Specific Behaviors (`\` separator, UNC, DOS paths)

## Windows Path Separators

How should the spec handle Windows separator (WS) support?

- They conflict with the escape operator (i.e. `foo/bar \[biz\]/*`)
- Some libraries support normalizing them to UNIX separators.
- quietly normalizes
- `zeptomatch` TODO: see how it handles the normalization
- `minimatch` matches Windows separators only on Windows
- requires UNIX separators
- `micromatch`
- `picomatch`

### Decisions

- [ ] How should the spec explicitly define WS handling?
- Forbid any WS? Allow normalizing? Require normalizing?

## [UNC Paths](https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats#unc-paths)

Universal naming convention (UNC) paths are special Windows-exclusive paths that are mainly intended for accessing network resources

Format: `\\{server/hostname/ip}\{share name}\{path}`

Example: `\\nas\data\foo\bar.txt`

### Decisions

- [x] Explicitly do not support UNC paths, too much complexity.

## [DOS Decvice Paths](https://learn.microsoft.com/en-us/dotnet/standard/io/file-path-formats#dos-device-paths)

Examples:
- `\\?\C:\Test\Foo.txt`
- `\\.\Volume{b75e2c83-0000-0000-0000-602f00000000}\Test\Foo.txt`
- `\\.\UNC\Server\Share\Test\Foo.txt`
- `\\.\BootPartition\Test\Foo.txt`

### Decisions

- [x] Explicitly do not support DOS Device paths, too much complexity.