Erk
Erk
I think this is ready for a wider review.
Is the "rustc-dev" component installed?
This does not seem to work with indexing that does not use usize as the index, for example it does not seem to catch the following panic: ```rust fn main()...
I would think that it would be better to have a `parse_optioned` method that takes an option struct. Then there could be a `parse` method that is strict and a...
I think of it like this ```rust fn parse_optioned(input: &str, config: Config) -> Result; fn parse(input: &str) -> crate::Result { parse_optioned(input, Config{/* Strict config */} } fn parse_relaxed(input: &str) ->...
In the example I provided the Cofig is user configurable. You could for example have a config builder or similar. But there are just default configs if tuning is not...
I think I would like the struct way more than the tuple.
Maybe also change `maintenance = { status = "experimental" }` though going by the [docs](https://doc.rust-lang.org/cargo/reference/manifest.html#the-badges-section) it seems like it is not used so possible just remove it?
One possible solution would be to select Vec when the features are `any(all(feature = "std", not(feature = "no_std")), all(feature = "std", feature = "no_std"))` and then make the heapless vec...
I think this is more of a documentation issue as making a function async means something specific which is not the case here.