Gimbles

Bump

Bump

I mean... I'm not exactly *surprised* that Rustc is taking more than 32 gigabytes of memory to compile **30000** patterns in a single match statement.

@chenyukang Remember to squash your commits 👏🏻

While this [does ICE on stable](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=bb9cd9f84db1c28090463bd6884be53e), it [doesn't on latest nightly](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=bb9cd9f84db1c28090463bd6884be53e).

Well, yes, it's still an ICE. But it is now fixed!

That issue title is..not particularly ideal.

Oh dear, I didn't think of that while making the PR. 😅 A possible solution could be checking if the current token is for initializing an item? Like, struct/enum/macro, etc.

1. This could be the `macro` keyword, as well. 2. That looks *alright*, ideally the repeated block could be prevented using a macro? I'm afraid that might slightly overengineer it,...

The documentation seems alright? Yes, `parse` returns a `Result` -- The example is calling `Result::ok` to convert `Result` to `Option` and *then* using `Option::unwrap_or_default`.