More complex options for comments about combine-language HOT 6 CLOSED

That seems a fair change to make. I just followed parsec which only has strings as well and I wasn't aware of any languages which have multiple way of writing the same comment type.

from combine-language.

It's not terribly common, you're right. Another use-case would be if you're writing an interpreter and you want to ignore shebang lines starting with #! and your line comments begin with a different sigil.

from combine-language.

#! could be handled easier without this lib though since it only appears in one place. Just add optional(string("#!") ...).with(yourparser) at the entry point of the parser.

I guess the only problem with this change might be how to handled nested comments (if this gets added, Parsec.Token has optionally support for nested comments). I think it should still be alright though.

from combine-language.

#! could be handled easier without this lib though since it only appears in one place.

True, good point.

from combine-language.

24c1279 resolves this though it may be good to revisit the implementation since it might not be as efficient as it can be/not generate good error messages.

from combine-language.

0.6.0 is on crates.io with this change now.

from combine-language.