Stephan Renatus a75b74db15 ast: add every future keyword (parser, internal representation) (#4179) ...

* ast: add 'every' future keyword, parser support, scaffolding

With this commit, "every x in xs { ... }" and "every k, v in { ... }"
will be parsed into a new struct, which is basically

    Every {
      Key, Value *Term
      Domain *Term
      Body Body
    }

This includes the required to changes to visitors, comparisons, copy, ...
all the ceremony required to introduce a new keyword.

* format: format every statements

* ast: hide 'every' from capabilities for now

With this change,

- capabilities.json will NOT mention "every"
- "import future.keywords" will NOT get you "every"
- "import future.keywords.every" will complain about "every" being unknown

In tests, we're passing an unexported field in `ast.ParserOptions`,
which makes the parser treat "every" like it would eventually be
treated when unveiled.

The formatting tests are bluntly SKIPPED for now, to be re-enabled later.

---------------
NB: The work on "every" is ongoing.
Rewriting and evaluation follows. When it's documented, we'll unhide it.
---------------

Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>

2022-01-18 10:32:20 +01:00

..

testfiles

ast: add every future keyword (parser, internal representation) (#4179)

2022-01-18 10:32:20 +01:00

format_test.go

ast: add every future keyword (parser, internal representation) (#4179)

2022-01-18 10:32:20 +01:00

format.go

ast: add every future keyword (parser, internal representation) (#4179)

2022-01-18 10:32:20 +01:00