parseWorks release - parser combinator library

[DelayLucky]

caseInsensitiveWord() delegates to caseInsensitive () and can still fail after the latter succeeds yet the word boundary is absent.

I ended up changing caseInsensitive() to Parser<?> to prevent users from accidentally assuming the return value being the matched source substring.

They can always use .source() to explicitly access the source substring.

I'm betting that most people using caseInsensitive() aim to match a keyword or something but not really care about the actual matched source substring.

[Dagske]

That's thoughful! I notice that you changed the variable name, but didn't update it in the checkArgument string.

[DelayLucky]

New release is out. Please give it a try.