A lot of the test left operands are invalid in native Elixir, which
means a new rule is needed f...

Fail back to doTest(true) for tests that are not expected to pass yet.

Allow for fewer doTest(true)s.

With the new understanding outlined in ELIXIR_BNF_DESIGN.md, it is no
longer necessary to test d...

Match naming scheme of AtNumeric.

It wasn't used more than once and so just added a stack level.

Rule did not end up being used anywhere, so just adds a stack level.

For non-numeric, the qualifier was before the operator name, but for
numeric it was after the op...

Rule is private, but only used in one place, so remove it will eliminate
a stack level.

The outer numeric rule, which combined charToken and number is actually
useful, while the number...

It is only used in one place and eliminating it will remove a stack
level, class, and interface.

I have no idea why I thought giving the qualified name was a good idea
at the time.

There is a failing test case, NonNumericUnaryOperation, where the
expected format has the unaryO...

Includes general design for structuring right-associative infix
operators.

Also change from simple doTest(true) to
assertParsedAndQuotedCorrectly().

Rule renames affected errors.

Test was not updated for change that required a valid decimal digits
immediately after DECIMAL_M...

Use `operand operation*` with `left operation` to limit backtracking.
Allow noParenthesesManyArg...

Remove fall through to leftOperand at bottom of rightOperand. Requires
expression to try, right...

Only valid digits may immediately follow `.` for it to count as a
decimal mark, otherwise `.` is...

First failure is `@1.identifier` not working because the `1.` is being
parsed as a broken decima...

Then charToken can cast it and call codePoint like with
hexadecimalEscapeSequence. Fixes quotin...

Have hexadecimalEscapeSequence implement EscapeSequenc so that the 2nd
child of charToken can be...

EnclosedHexadecimalEscapeSequence fails on quoting.

Error updated due to new rule names.

Replaced by MatchedNonNumericAtRightOperationParsingTestCase.

Include the for loop used in the pattern for LeftOperand in RightOperand
too.

Allows for nesting prefix operations inside themselves.

Only broke out working tests. Non-working tests for currently
non-reimplemented operations are ...

Use new name for rule that combines old
noParenthesesManyArgumentsUnqualifedCall and
noParenthes...

Extract out a matchedOperandExpression which is either a
noParenthesNoArgumentsUnqualiedCallOrVa...

Change * on right operations to + to ensure that at least one right
operation is in right expres...

Test quoting of `@function positional, keyword_key: keyword_value`.

Test quoting of `function positional, keyword_key: One.Two`.

Test quoting of `function positional, keyword_key: Alias.identifier`.

Hand to differentiate bet...

Involved breaking up CHAR_TOKEN from a lexeme to CHAR_TOKENIZER for `?`
and the CHAR_LIST_FRAGME...

Test quoting of `function positional, keyword_key: 1.0e-1`.

Test quoting of `function positional, keyword_key: []`

Test quoting of `function positional, keyword_key: "string"`

Test quoting of
```
function positional, keyword_key: """
stri...

Test quoting of `function positional, keyword_key: 'charListLine'`.

Test quoting of

```
function positional, keyword_key: '''
cha...

Test quoting of `function position, keyword_key: ~r{sigil}`.