I dont see any equivalent logic on the js side. I seems that caml_assume_no_perform completely forbid effect with wasm while effects could still happen with js after resuming a stack ? I must admit...
```
let doc =
"Select an implementation of effect handlers. [$(docv)] should be one of $(b,cps) \
or $(b,double-translation). Effects won't be supported if unspecified."
```
> @hhugo Is there something remaining for this to be merged? Do you consider [ocaml/dune#11222](https://github.com/ocaml/dune/pull/11222) to be a necessary prerequisite?
[ocaml/dune#11222](htt...
What about doing something similar to `target` above.
```ocaml
type effects_backend =
| `Cps
| `Double_translation
| `Jspi
| `Not_supported
| `None
let effects_ : effects_backen...
> @hhugo Is there something remaining for this to be merged? Do you consider [ocaml/dune#11222](https://github.com/ocaml/dune/pull/11222) to be a necessary prerequisite?
I'd like to do another r...
hhugo
created a review comment on a pull request on
ocaml/dune
The downside is that it increases the number of dune rules registered in dune. One rule per lib per config in `Config.all`. We currently have 27 config on master. Having cps, double_translate, jsp...