-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Disjointed ways of finding files #13
Comments
One concern raised on reddit for wrapping walkdir is the very nature of wrapping it. For a higher-level, ergonomic API, do we need to expose the full power of the API? I feel like we can assume the users of the library are already sacrificing performance for ergonomics. walkdir on the other hand was heavily designed for performance. This provides a way for alternatively exposing walkdir in a simple way that integrates with the rest of the crate. |
I think you didn't complete this sentance 😃
I agree with this to an extent. The main reason that
I actually hadn't considered this. In some ways the only APIs we need are:
This is really all I have needed for some pretty complex applications. Sorting the output, breadth-first, etc are not often needed features and while the |
Starting from requirements, which you just gave, I think will be important for this. I think another good angle is "what do other high level APIs do" (Python's pathlib being the one I'm most familiar with but they intentionally left functionality off of it like I think what you listed works well. |
(Originally on reddit)
In looking at the holistic API
The text was updated successfully, but these errors were encountered: