-
Notifications
You must be signed in to change notification settings - Fork 6
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
Buffered parse #11
Buffered parse #11
Conversation
This is a very interesting approach; thank you! This has fallen off my radar for ages, but I'd very much like to play around with your approach here and see how I feel about it; being able to easily parse digits and such is something I've run into quite a lot, and so something like this would be a great addition! |
It might not be worth having |
Intstead of choosing the buffer type when doing parsing choose the buffer based upon `Tokens`'s type. This allows zero-copy parsing by re-using the underlying token buffer if one exists. If one doesn't exist it enables opaque handling of creating a buffer.
Changed. Now buffer has an associated type which is selected by the particular |
Closed in favor of #13 |
Add parsing of iterators with the
str::parse
function.Allows re-use of a datatype's
FromStr
implementation and easily changing the temporary buffer type so allocations can be done on the stack (no_std
compatible) using ex.heapless::String
orcrate::buffered::StackString
instead of naively using astd::string::String
on the heap.