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
It is stated in the documentation that "If a glob expression consists solely of a tree wildcard, then it matches any and all paths and the complete contents of any and all directory trees, including the root".
I have the following file structure in /tmp/files:
Thanks for the report! Yes, this is definitely a bug! Your first example should indeed yield the entire contents of the directory.
When given an empty collection, not constructs a bogus Any token. This particular API has already been fixed in 76afaa1. However, there isn't yet a test for this and only not has been fixed: this can still happen via the any function in the crate root. To be sure, I just tried a test very similar to this one where the collection is empty and confirmed the correct behavior.
I'll leave this issue open until I land an appropriate test and change all of the concerned APIs such that they don't construct garbage from empty collections.
Hello,
I might have noticed a bug.
It is stated in the documentation that "If a glob expression consists solely of a tree wildcard, then it matches any and all paths and the complete contents of any and all directory trees, including the root".
I have the following file structure in
/tmp/files
:with the following Rust code:
The output is:
when i remove the negation:
it works:
Did i miss anything ?
The text was updated successfully, but these errors were encountered: