prometheansacrifice

I had some trouble writing handlers beyond the provided examples. This could be because of the rapid changes seen in the repository. The following never worked ```re req.request.target |> Uri.of_string...

We could have a separate page/section documenting every error and provide more info and a possible solution where applicable

If for some reason, the initial bootstrapper fails (network failure, bad cache etc), creation of dune files in the project could get interrupted - the dune files that trigger the...

Pesy atleast 4.6.1000 We need a pipeline on the CI to test against all the compiler versions.

EXPERIMENTAL

Using the trick used to figure out library path of an imported library, we could also determine other variables like `#{@opam/zarith.lib}`, `#{@opam/zarith.etc}` etc - paths in the install tree of...

Atdgen needs rules like these ```sexp (rule (targets example_j.ml example_j.mli) (deps example.atd) (action (run atdgen -j -j-std %{deps}))) (rule (targets example_t.ml example_t.mli) (deps example.atd) (action (run atdgen -t %{deps}))) ```...

Figure out a Module_test.re convention as seen in the JS world

7

Dune let's us abstract a package by using a module of the same name as the package. If `Foo.re` is present in a package namespaced under `Foo`, other modules can...

The CI pipeline for pesy includes a setup that display the checksum for the prebuilt pesy binaries. Projects bootstrapped using pesy can benefit from such a CI project too

Specifying certain configs can get ambiguous at times. ```json "modes": "best exe", "modes": ["best", "exe"], "modes": ["best exe", "best object"] ``` The last one isn't supported yet, but seems perfectly...