-
Notifications
You must be signed in to change notification settings - Fork 13
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
Module hierarchy like in nom? #23
Comments
Something definitely needs to be done wrt this, yep |
This could be a first step |
Yeah, sounds like a good start to me. I was also thinking about creating modules like nom's |
yup, it's a good idea to have modules, better have them now and add stuff later, because changing module paths later will be a breaking change |
Ok, let's go with the top-level modules of nom then as a starting point, plus what @Keruspe said in the first comment above? I can prepare a PR for that if that sounds fine to everybody. |
This is fixed by a265b1c and follow-up commits now |
Currently all types are directly at the top-level of the crate. It potentially makes sense to move them into various sub-modules similar to how it's done in nom.
As part of that, the compat
std::io
module could also be moved into a nicer place.And maybe we could also move the macros out of the way into some kind of legacy module and mark them as deprecated :)
What do you think?
The text was updated successfully, but these errors were encountered: