You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While globset can match on arbitrary OS strings, it cannot accept an arbitrary OS string as a glob. The link above gives an example. Here it is in code form (which currently prints false):
To be clear, this particular program shouldn't succeed because a UTF-8 string is given to Glob::new. But there should be a way to, for example, call Glob::new(some_os_str). On Unix, that OS string can be arbitrary bytes.
(The globset crate is due for an API refresh and likely a rewrite of its internal parser anyway. This should be fairly easy to support.)
The text was updated successfully, but these errors were encountered:
Initially reported here: rust-lang/glob#78
While globset can match on arbitrary OS strings, it cannot accept an arbitrary OS string as a glob. The link above gives an example. Here it is in code form (which currently prints
false
):To be clear, this particular program shouldn't succeed because a UTF-8 string is given to
Glob::new
. But there should be a way to, for example, callGlob::new(some_os_str)
. On Unix, that OS string can be arbitrary bytes.(The globset crate is due for an API refresh and likely a rewrite of its internal parser anyway. This should be fairly easy to support.)
The text was updated successfully, but these errors were encountered: