1
91%
master: 91%

Ran 24 May 2024 05:04PM UTC

Files 18

Run time 0s

Badge

Embed ▾

Committed 24 May 2024 05:01PM UTC coverage: 89.669% (-0.1%) from 89.795%

Job # 9227473635.1

Build Type

push

github

Committed by

wkhere

Commit Message

fix fake-eof and related behavior in lex/parse

Lexer is now sending explicit tFAIL token after error. That token is
interpreted in the parser accordingly. The assumption is that, contrary
to parse errors, it doesn't make sense to continue processing input
after a lex error, as there's usually a cascade of mess afterwards.
Even if I could do better than this assumption, that's the silent
behavior of previous code, which was misbehaving anyway - see below.

In addition to sending tFAIL token by lexer and interpreting it in the
parser (eg. there are two final tokens now, examined by parser.matchEnd
and parser.checkEnd; the error printing is fixed as well), there is also
a check inside block parsing to return earlier after tFAIL. This can be
extended in the future for other parts of the parser.

Now about a previous subtle bug: tEOF after tERR was read by
parser.advance only because it was zero-value from closed channel.
It could be seen as 'line 1:1: error at end: ...' error message,
even though 1:1 is definitely not end of the stream.
Parser was relying on this behavior, so for example after starting
tokens with iota+1 it went into infinite loop.

Run Details

1545 of 1723 relevant lines covered (89.67%)

0.98 hits per line

wkhere / bcl / 9227473635 / 1
91%
master: 91%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 9227473635.1

wkhere / bcl / 9227473635 / 1 91% master: 91%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 9227473635.1

wkhere / bcl / 9227473635 / 1
91%
master: 91%

README BADGES
x