Johan Fylling

A fix for this issue has been merged to `main`, and will be part of the next OPA release. Please note that Early Exit only applies to rules/functions with results...

Closing this PR, as the breaking API changes makes it very unlikely that this will ever get merged. The lazy-object optimization has already been merged to main in #6060.

Wouldn't the same line of arguing hold true for _any_ new check added to strict mode? The idea behind strict mode is that it will reject any policy that isn't...

Alternatively, we flip it, and make double `#` signify a comment within metadata: ```rego # METADATA # title: foo ## TODO: remember to change this # description: bar package p...

To accommodate projects that are already using custom 1st level annotations, we should provide a way to opt-out; as refactoring might be a big undertaking. One way to accomplish that...

Opinion: although it can be argued it's more readable to separate METADATA blocks with newlines, there is no real reason to disallow this in the parser; and should instead be...

> Comprehensions aren't allowed to be used anywhere else in the language like that I don't think we need to redefine how comprehensions work. It should just be enough to...

My reasoning behind introducing `` is to make it possible to define a comprehension that doesn't return a collection. Of course, we could also add this behavior to e.g. the...

Changing `a` to define an array `a := [1, 2, 3, 4]` makes the type-checker happy. Naturally, this will however make the equality in `output` fail (set != array, even...

The build command respects the `--v1-compatible` flag, and `opa build -O1 --v1-compatible` will output: ```rego package test p if { input.x = 1 } ``` Given this fact, I don't...