Stephan Renatus

> Can I use the contributor's channel to ask questions about the implementation? Of course, that's what it's for 😃

You could also open a PR right away. It's easier to comment on that etc

The concrete error is irrelevant, but on this occasion, it has cut of the interesting bit, not the "too cryptic" addendum: ``` => (use (*dir*/opa.bass)) error! call trace (oldest first):...

> @srenatus do you know which version of opa stops supporting any and all? OPA "1.0", but it's not clear yet when that's going to happen. That said, the linked...

> It's tempting to re-implement these functions as custom built-ins to avoid this concern, I'm not sure how hard that would be. Not hard. I believe @anderseknert has a snippet...

Contributions welcome! Happy to assist. The setup here could also be simpler than what OPA does: since no cgo is needed, we could use ko.

https://github.com/open-policy-agent/opa/blob/main/.github/workflows/post-merge.yaml#L160 should do it, at least the -edge images.

Is this still relevant? 0.39.0 is the latest release... 🤔

> So IIUC we'd need to add a musl build config to Wasmtime, and optionally use that in wasmtime-go? I suppose if wasmtime was pushing a musl c-api tarball, we...

I must be missing something, the latest release, https://github.com/bytecodealliance/wasmtime/releases/tag/v0.27.0, doesn't have anything for macos that isn't x86_64. We'd need that for starters, don't we?