Stephan Renatus

Is there consensus on how to do it? I presume we'll go with ```rego import future.keywords [every, contains, if] import data.other.policy [foo, bar as b] ``` ❓

It's fine. I just wanted everyone to be on the same page. I think an interesting question here is capabilities: How can we introduce this change so that the user...

@ashutosh-narkar What do you think? IMO, if we can make it backwards-compatible, it's a good idea to return the errors... For context, I think the code was written at a...

Tests don't use the wasm eval path iirc... I suppose that's worth fixing. And the overlying problem, too, of course. Thanks for reporting

Sent too early. That fail is at build time, before anything is evaluated.

So it only happens with `-t wasm`.

The example can be boiled down to ```rego package reproduction g(_) = true f(x) = g(x) ``` *However*, it's unclear to me what the desired outcome of that Wasm bundle...

> Regarding prioritization, while the pattern I shared above will not compile in a single package, we did manage to find a workaround and noticed that if we put the...

Using npm-opa-wasm?

@tristanls Whats your use case? Would passing `--prune-unused` to `opa build` help you, too? (See #5035)