Panic on consecutive "enclosing items" (lists, strings, maps)

[patataofcourse]

Example:

["game over & other shit", {gameover}] ["exit", None]

Panic shown:

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: InvalidDigit }', src/parsing/mod.rs:349:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

[patataofcourse]

Can confirm it still happens on commit 597b559

[patataofcourse]

Fix from 848b18a turned out to be p bad so I reverted it.
Basically these two expressions get interpreted as one due to the lack of delimiters. Probably gonna need to polish up a bunch of parser stuff to get it to work as intended.

The thing is - if the expression is "foo" [bar] "baz", the parser detects that this expression starts and ends with quotes, so it tries to get the index for this string. With "simplified" strings and brackets, instead of "0", this looks like "0" {0} "1", so it tries to parse 0" {0} "1 as a number, which obviously fails. The fix isn't adding an error message to this edge case, but avoiding it altogether.