This repository was archived by the owner on Jul 19, 2020. It is now read-only.
This repository was archived by the owner on Jul 19, 2020. It is now read-only.
Remove ambiguity regarding ! token after {capture} token #148
Description
Placing a
!after capture block is not allowed (but this restriction is only partially applied, which is also not ideal). This is done because some code innext_delimiterwould panic if it encounters a End token instead of an exact.Ideally the
!should be allowed after capture blocks, butnext_delimiterand the functions that utilize it may need to change in order to allow this.