Xiretza

There is indeed a multiple assignment, line 44 (assigning to `vector(0)`) needs to be moved outside the generate block, otherwise those elements are actually assigned from multiple processes. The error...

I'd say the expected output for the CI run on 8185ed8 would be: ``` GHDL 2.0.0 (2.0.0.r0.g8185ed878) [Dunoon edition] ``` However, the CI run was started before the tag was...

Yeah, you can't do that. The "rest" you return needs to be a subslice of your input.

Adding a macro seems overkill - how about if nom provided a ```rust struct StatefulStr; ```

It could even be generalized to this: ```rust struct StatefulInput { input: I, state: T, } ``` I'll wait for an opinion from @geal - if this sounds good, I'll...

I tried adding a `#[deprecated]` marker to the reexport to warn users about this early, but that doesn't actually work - see https://github.com/rust-lang/rust/issues/30827.

I agree that there are a lot of opportunities to improve the documentation - I think pull requests in this area are always welcome!

I'm having a hard time following your comment, and github issues aren't really the best medium to figure things like this out anyway - but if you want to join...

Please provide a minimal reproducer of your problem when reporting an issue. There's a reason this is a part of the issue template, which you seem to have ignored entirely....

I feel like hiding the old paths without adding deprecation warnings will lead to confusion. Code will compile silently, but when trying to understand what it does, the nom docs...