We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go version
go version devel +4a28707d55 Wed Jan 10 16:13:38 2018 +0000 linux/amd64
Yes.
https://play.golang.org/p/szEMiava76J
Given that this is Linux:
[a] <nil> [a] <nil> true <nil>
[a] <nil> [] <nil> true <nil>
I think this is broken, because the Match docs say:
On Windows, escaping is disabled. Instead, '\' is treated as path separator.
And, as you can see, Match works while Glob doesn't. CL incoming.
Match
Glob
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/87455 mentions this issue: path/filepath: fix escaped chars in Glob on non-Windows
path/filepath: fix escaped chars in Glob on non-Windows
Sorry, something went wrong.
03f27d5
No branches or pull requests
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What did you do?
https://play.golang.org/p/szEMiava76J
What did you expect to see?
Given that this is Linux:
What did you see instead?
I think this is broken, because the Match docs say:
And, as you can see,
Match
works whileGlob
doesn't. CL incoming.The text was updated successfully, but these errors were encountered: