Switch from deku
to cookie-factory
and nom
#10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
deku
is a bit overkill for a small parser like this. We don't have to perform any bit level manipulation nor is the format itself complex enough to warrant using a parser generatorThe switch also gets rid of proc macros and the
alloc
requirement (making this crate entirelyno_std
compatible)I'm not entirely sure whether the
deserialise
andserialise
functions are idiomatic tocookie-factory
/nom
(as in that they can be used in generator/parser chains)