1e16c22d03
Perviously we used token level lookbehind in the parser. That worked,
but only if the parser didn't have any ambiguity *at all*. Since the
parser has ambiguity it didn't work everywhere. In particular it failed
when parsing blocks in lambdas like `a -> {int b = a + 2; b * b}`.
This moves the hack from the parser into the lexer. There we can use
token lookbehind (same trick) to *insert* semicolons into the token
stream. This works much better for antlr because antlr's prediction
code can work with real tokens.
Also, the lexer is simpler than the parser, so if there is a place
to introduce a hack, that is a better place.
|
||
|---|---|---|
| .. | ||
| aggs-matrix-stats | ||
| ingest-common | ||
| lang-expression | ||
| lang-groovy | ||
| lang-mustache | ||
| lang-painless | ||
| percolator | ||
| reindex | ||
| build.gradle | ||