Closed mefyl closed 4 years ago
I'd like to keep csexp
minimal. In particular it is used by projects that don't currently depend on Base such as merlin, so let's not introduce a dependency on it.
For Lwt, the inter-op is now one simple functor application away, so yeah let's not be over-zealous :)
@mefyl are you happy to do the release in opam?
Sure thing, but never did before. Is there a walkthrough somewhere ?
It should be documented in the --help
of dune-release
. But basically, you need to:
dune-release
via opamdune-release tag
to add a git tag (it will fetch the version number from the changelog)dune-release
to do everything else, in particular create the opam-repo PR. The first time you run it, it will ask you a few questions such as your github username, etc...
The existing interface has been left untouched. The parser backend is now exposed and functorized over an arbitrary monad. The implementation is a bit verbose due to the lack of monadic binding syntax and the bareness of
Result
in 4.02.3.Further considerations :
Monad
interface definition instead of introducing it for the bazillion time, but that would require 4.03.