-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[new release] cstruct-async, ppx_cstruct, cstruct, cstruct-unix, cstruct-sexp and cstruct-lwt (4.0.0) #13748
Conversation
…uct-sexp and cstruct-lwt (4.0.0) CHANGES: - Sexplib is now an optional library for the base `Cstruct` module. A new `Cstruct_sexp` module has been introduced with the serialiser functions, contained within the `cstruct-sexp` opam package. To convert old code, simply use `Cstruct_sexp.t` instead of `Cstruct.t` in a record type for which you are using `[@@deriving sexp]`. This is a type alias to `Cstruct.t` but also has the right sexp-conversion functions in scope. There is an example of this in the `ppx_test/with-sexp` directory in the source repo. When you have converted and released your library, add an opam constraint of `cstruct {>="4.0.0"}` to your own opam packages to ensure that they pick up this version of the library. (fixes mirage/ocaml-cstruct#222, @avsm) - JavaScript stubs are now installed using the jsoo mechanism rather than a manual specification (mirage/ocaml-cstruct#241 @jonludlam) - Use computed versions in opam files to ensure that dependent opam packages such as cstruct-async get the same base version of cstruct to avoid mismatches. (@avsm) - Add a ppx test suite to checks that all error paths in ppx handling are reachable and have meaningful location info (mirage/ocaml-cstruct#238 @emillon)
☀️ All lint checks passed 86ed182
☀️ Installability check (10889 → 10895)
|
…release-cstruct-4.0.0
4.03-4.05 are failing with:
Do you want to lower bound ocaml in |
I know you are ludicrously busy, but please have also a look at ther revdeps: lots of things are failing due to the sexp split. It may be important to add upper bounds before merging this PR. It looks also like some packages were getting Sexplib as a transitive dependency from cstruct. I think the three packages that make everything else fail are:
|
Thanks for the triage @mseri! I'll look the revdeps and fixes now |
The ppx failure is a bit frustrating, since only cstruct-unix depends on ocaml>=4.06, but the CI failing since its trying to install all packages... |
This nocrypto failure is concerning
|
Related issue: mirleft/ocaml-nocrypto#156 |
…release-cstruct-4.0.0
…release-cstruct-4.0.0
due to making sexp optional in cstruct, see ocaml#13748
due to making sexp optional in cstruct, see ocaml#13748
…release-cstruct-4.0.0
Access C-like structures directly from OCaml
CHANGES:
Sexplib is now an optional library for the base
Cstruct
module.A new
Cstruct_sexp
module has been introduced with the serialiserfunctions, contained within the
cstruct-sexp
opam package.To convert old code, simply use
Cstruct_sexp.t
instead ofCstruct.t
in a record type for which you are using[@@deriving sexp]
.This is a type alias to
Cstruct.t
but also has the rightsexp-conversion functions in scope. There is an example of this
in the
ppx_test/with-sexp
directory in the source repo.When you have converted and released your library, add an
opam constraint of
cstruct {>="4.0.0"}
to your own opampackages to ensure that they pick up this version of the library.
(fixes sexplib dependency mirage/ocaml-cstruct#222, @avsm)
JavaScript stubs are now installed using the jsoo mechanism
rather than a manual specification (Javascript packaging fixes mirage/ocaml-cstruct#241 @jonludlam)
Use computed versions in opam files to ensure that dependent
opam packages such as cstruct-async get the same base version
of cstruct to avoid mismatches. (@avsm)
Add a ppx test suite to checks that all error paths in ppx
handling are reachable and have meaningful location info (Test ppx errors mirage/ocaml-cstruct#238 @emillon)