From: Alan Schmitt <email@example.com> To: "lwn" <firstname.lastname@example.org>, "cwn" <email@example.com>, firstname.lastname@example.org, email@example.com Subject: [Caml-list] Attn: Development Editor, Latest OCaml Weekly News Date: Tue, 12 Jan 2021 10:47:26 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) [-- Attachment #1: Type: text/plain, Size: 19040 bytes --] Hello Here is the latest OCaml Weekly News, for the week of January 05 to 12, 2021. Table of Contents ───────────────── Marshal determinism and stability Sedlex + Menhir parser for both tty and file parsing First release of awa-ssh Introducing Feather: A lightweight shell-scripting library for OCaml postdoc researcher and research engineer positions for CHERI and Arm verification First ocb (OCaml Badgen) release Release of OCaml-Git v3.0 and co Other OCaml News Old CWN Marshal determinism and stability ═════════════════════════════════ Archive: <https://discuss.ocaml.org/t/marshal-determinism-and-stability/7041/28> Continuing this thread, David Allsopp said ────────────────────────────────────────── A couple of notes on `Marshal', which I don't think have been covered • Although the guarantee is only between identical versions of OCaml, the implementation actually goes to considerable lengths to maintain backwards compatibility (so a value _written_ by older OCaml remains _readable_ in newer OCaml). Our own testsuite, for example, indirectly [includes a test which unmarshals a 3.12.1 value]. I don't know exactly how far back the support goes. • As it happens, the change which affected Unison in 4.08 was the first breaking change to Marshal since either 4.00 or 4.01. The fact that it doesn't break often (and that the two code paths - at least at present - are small) meant I have suggested a few months back that we could in future add an additional flag in the style of `Compat_32' to allow values to be written in a way which should be readable on older versions of OCaml. Indeed, it's small enough that flags could be added for the changes in 4.08 ([PR#1683]) and in 4.11 ([PR#8791]). • Neither point undermines using alternative formats either for network serialisation or persistent storage, for the many reasons discussed above! [includes a test which unmarshals a 3.12.1 value] <https://github.com/ocaml/ocaml/blob/trunk/testsuite/tests/lib-hashtbl/compatibility.ml> [PR#1683] <https://github.com/ocaml/ocaml/pull/1683> [PR#8791] <https://github.com/ocaml/ocaml/pull/8791> Sedlex + Menhir parser for both tty and file parsing ════════════════════════════════════════════════════ Archive: <https://discuss.ocaml.org/t/sedlex-menhir-parser-for-both-tty-and-file-parsing/7055/1> Bernard Sufrin announced ──────────────────────── I am a great fan of Menhir, and have used it in several private language projects, using the ulexing scanner generator to provide Unicode-capable scanners. Alarmed by the obsolescence of ulexing, and needing a utf8-capable scanner in a hurry I decided to (teach myself to) use Sedlex. On the whole the experience was very satisfactory, and I found it straightforward to produce a variant of the sedlexing library which supports buffers with variable chunk sizes, thereby enabling efficient lexing on channels connected to files as well as immediately responsive lexing on channels connected to terminals. I also wanted to teach myself how to use the error-reporting, incremental, interfaces to Menhir-generated parsers. In the hope that it might be useful to others facing the same learning task, or the problem of adapting Sedlex for efficient interactive use, I have placed the example mock-S-Expression parser that resulted from this excursion in: [Git Repository: github.com/sufrin/InteractiveSedlexMenhirExample] [Git Repository: github.com/sufrin/InteractiveSedlexMenhirExample] <https://github.com/sufrin/InteractiveSedlexMenhirExample> First release of awa-ssh ════════════════════════ Archive: <https://discuss.ocaml.org/t/ann-first-release-of-awa-ssh/7057/1> Hannes Mehnert announced ──────────────────────── I'm happy to announce that `awa-ssh' (<https://github.com/mirage/awa-ssh>) has just been merged into opam-repository. It is a pure OCaml implementation of the ssh (secure shell, <https://en.wikipedia.org/wiki/SSH_(Secure_Shell)>) protocol. This is the initial release, please report issues you encounter. It was initially developed by Christiano Haesbaert in 2016, and revived mid-2019 by myself and in 2020 it was migrated to the MirageOS organization on GitHub for further development and maintenance. Both client and server code are present in the library (pure code in the main awa package), though the awa-lwt package implements only a server, and the awa-mirage package implements only a client. Tests and examples are in the test subdirectory. The MirageOS client has been successfully used to clone git repositories (on private servers, on GitHub, etc.). It supports apart from RSA keys also ED25519 keys (and key exchanges). Introducing Feather: A lightweight shell-scripting library for OCaml ════════════════════════════════════════════════════════════════════ Archive: <https://discuss.ocaml.org/t/introducing-feather-a-lightweight-shell-scripting-library-for-ocaml/7059/1> Charles announced ───────────────── I wrote a shell scripting library called [Feather]. I like idea of writing bash-like code quickly, later being able to intersperse OCaml to add more typeful components as needed. It's kind of like [Shexp] but without the monadic interface and with Async support. ([Feather_async]) There's a tutorial and some examples in the link above but here's a quick taste: ┌──── │ open Feather │ │ let lines = find "." ~name:"*.ml" │ |. tr "/" "\n" │ |. map_lines ~f:String.capitalize │ |. sort │ |. process "uniq" [ "-c" ] │ |. process "sort" [ "-n" ] │ |. tail 4 │ |> collect_lines │ in │ String.concat ~sep:", " lines |> print_endline └──── Let me know if you have any feedback! And feel free to file bug reports [here]. Hope it ends up being useful, entertaining, or both! [Feather] <https://hg.sr.ht/~etc/feather> [Shexp] <https://github.com/janestreet/shexp/> [Feather_async] <https://hg.sr.ht/~etc/feather_async> [here] <https://todo.sr.ht/~etc/feather> postdoc researcher and research engineer positions for CHERI and Arm verification ═════════════════════════════════════════════════════════════════════════════════ Archive: <https://sympa.inria.fr/sympa/arc/caml-list/2021-01/msg00023.html> Peter Sewell announced ────────────────────── We are looking for postdoctoral researchers and postdoctoral or postgraduate research engineers to help develop semantics and verification to improve the foundations and security of mainstream computer systems, for CHERI and Arm system software verification, at the University of Cambridge. OCaml expertise to help develop verification tools will be especially welcome. Closing date 13 January 2021 - see the advert <http://www.jobs.cam.ac.uk/job/28012/>. First ocb (OCaml Badgen) release ════════════════════════════════ Archive: <https://discuss.ocaml.org/t/ann-first-ocb-ocaml-badgen-release/7073/1> zapashcanon announced ───────────────────── A few days ago, I released [ocb]. It's a library and a command-line tool to generate SVG badges. To get started quickly: ┌──── │ ocb --label Hello --color green --style flat --labelcolor white --status Goodbye └──── Will gives this result: [SVG example]. My first use case was [To.ml] where I'm using [bisect_ppx] to generate and deploy a [coverage report]. I wanted to display the coverage percentage in the README and tried existing tools but wasn't fully satisfied as they didn't work or were failing randomly. Now, [I'm generating the badge directly in a GitHub action]. The project was inspired by [badgen]. I still have to add support for icons and to improve the documentation but it's usable. [ocb] <https://github.com/ocamlpro/ocb> [SVG example] <https://raw.githubusercontent.com/OCamlPro/ocb/master/example/cli.svg> [To.ml] <https://github.com/ocaml-toml/To.ml> [bisect_ppx] <https://github.com/aantron/bisect_ppx> [coverage report] <https://ocaml-toml.github.io/To.ml/coverage/> [I'm generating the badge directly in a GitHub action] <https://github.com/ocaml-toml/To.ml/blob/6ac580848ad1d34ec3032da8672bbd9aca203cc4/.github/workflows/deploy.yml#L34> [badgen] <https://github.com/badgen/badgen> Release of OCaml-Git v3.0 and co ════════════════════════════════ Archive: <https://discuss.ocaml.org/t/ann-release-of-ocaml-git-v3-0-and-co/7076/1> Ulugbek Abdullaev announced ─────────────────────────── We, the [`ocaml-git'] team, are happy to announce a new major release of `ocaml-git v3.0' and related libraries. [`ocaml-git'] <https://github.com/mirage/ocaml-git> Release Notes ╌╌╌╌╌╌╌╌╌╌╌╌╌ OCaml-Git v3.0 ┄┄┄┄┄┄┄┄┄┄┄┄┄┄ [*OCaml-Git*] is a library that implements `git' format and protocol implementation in pure OCaml. The library is used by libraries such as [`irmin'], a git-like distributed database, or [`pasteur'], a MirageOS unikernel-based snippet storage service. [*OCaml-Git*] <https://github.com/mirage/ocaml-git> [`irmin'] <https://github.com/mirage/irmin> [`pasteur'] <https://github.com/dinosaure/pasteur> Changes ┈┈┈┈┈┈┈ The main goal behind this major release was to get better compatibility with various platforms, including [~MirageOS~](mirage.io), 32-bit platforms, and `js_of_ocaml'. In order to achieve that, we broke down `ocaml-git' into several components, which are represented as sub-libraries. We will describe some of those components later in this post. Along with better support for various platforms, `ocaml-git 3.0' also comes with SSH support for `fetch/push' and various bug fixes. The rest of the changes are mostly internal and pave a way for interesting features such as a full-blown `git' [garbage collector] and wire protocol v2 ([announcment] and [spec]). *References:* • Full [changes list] • [PR] that introduced the major rewrite of `ocaml-git' — In the new version of `ocaml-git', we try to have better separation of concerns by breaking some of the `ocaml-git' components into sub-libraries, which do not contain `git'-specific logic and can be reused for other purposes. [garbage collector] <https://git-scm.com/docs/git-gc> [announcment] <https://opensource.googleblog.com/2018/05/introducing-git-protocol-version-2.html> [spec] <https://github.com/git/git/blob/master/Documentation/technical/protocol-v2.txt> [changes list] <https://github.com/mirage/ocaml-git/blob/master/CHANGES.md> [PR] <https://github.com/mirage/ocaml-git/pull/395> Carton ┄┄┄┄┄┄ Git uses [PACK files] to store old git objects such as commits and transfer objects over wire using git's wire protocols (`git-nss' library mentioned below implements [v1] of the protocol; [v2] implementation is in progress). [*Carton*] is a library to work with PACK files. The library does not contain git-specific code, so one can easily reuse the library and PACK format for non-git objects. One can see how `ocaml-git' uses `carton' for its purposes [here]. *References:* • [PR] that introduces `carton' [PACK files] <https://github.com/git/git/blob/master/Documentation/technical/pack-format.txt> [v1] <https://github.com/git/git/blob/master/Documentation/technical/pack-protocol.txt> [v2] <https://github.com/git/git/blob/master/Documentation/technical/protocol-v2.txt> [*Carton*] <https://github.com/mirage/ocaml-git/tree/master/src/carton> [here] <https://github.com/mirage/ocaml-git/tree/master/src/carton-git> [PR] <https://github.com/mirage/ocaml-git/issues/375> Git-NSS (Not So Smart) ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄ When one wants to synchronize with a remote repository using git, they need to use `git fetch/push'. Communication and synchronization/negotiation is defined by git *wire protocol*, which has two versions: older version 1 and newer leaner version 2. The protocols are defined for four wire transports: HTTP(S), SSH, and `git://' (TCP). [`Not-So-Smart'] library is a library that allows for such synchronization based on the git wire protocols but without git-specific code, meaning that files being fetched do not need to be git objects or that there is no assumptions on the "repository" that one is synchronizing with. So, as well as `carton', the library aims to be reusable for other purposes. This release features support for SSH using [awa-ssh] by @hannesm (see [the release]), support for [partial-clone] (of various `depth'), and memory consumption fixes for unikernels. *Note 1:* The library's name "Not so smart" is a play on the git's "smart" protocol, a part of wire protocol v1 over HTTP(S) transport. *Note 2:* only client side logic is implemented for wire protocols. The server-side is planned but not yet implemented. One can use `git' as the server for now. [`Not-So-Smart'] <https://github.com/mirage/ocaml-git/tree/master/src/not-so-smart> [awa-ssh] <https://github.com/mirage/awa-ssh> [the release] <https://discuss.ocaml.org/t/ann-first-release-of-awa-ssh/7057> [partial-clone] <https://git-scm.com/docs/partial-clone> Mimic ┄┄┄┄┄ [*Mimic*] is a small reimplementation of [`conduit'], a library that helps to abstract over a transport protocol such as HTTP(S) or SSH. In other words, the code using `mimic' can deal not with different types that represent an HTTP or SSH connection, but just deal, e.g., read from or write to, with a `flow' value, which hides protocol-specific details under its hood. — There are several independent libraries that were upgraded along with `ocaml-git 3.0'. [*Mimic*] <https://github.com/mirage/ocaml-git/tree/master/src/mimic> [`conduit'] <https://github.com/mirage/ocaml-conduit> Duff v0.3 ┄┄┄┄┄┄┄┄┄ [*Duff*] is a library that implements git's [`libXdiff'] (`xdiff' algorithm) in OCaml. PACK files use a binary diff algorithm, `xdiff', to compress binary data. More on the project [page] and release [notes] for `ocaml-git 2.0'. [*Duff*] <https://github.com/mirage/duff> [`libXdiff'] <http://www.xmailserver.org/xdiff-lib.html> [page] <https://github.com/mirage/duff> [notes] <https://discuss.ocaml.org/t/ann-ocaml-git-2-0/2740> Changes ┈┈┈┈┈┈┈ This release fixes the support for 32-bit architecture platforms. Encore v0.7 ┄┄┄┄┄┄┄┄┄┄┄ [*Encore*] is a library that can create an encoder/decoder based on the format given. It also ensures isomorphism by construction. [*Encore*] <https://github.com/mirage/encore> Changes ┈┈┈┈┈┈┈ Extensive changes to the API. See the project page. Decompress v1.2.0 ┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄ [*Decompress*] is an OCaml implementation of certain decompression algorithms such as `Zlib', `Gzip', etc. [*Decompress*] <https://github.com/mirage/decompress> Changes ┈┈┈┈┈┈┈ `ocaml-git 3.0' uses new version of `decompress' with extensive performance improvements documented in *Tarides's* blog [API changes] and [performance improvements]. We'd be happy to get your feedback or questions! :-) [API changes] <https://tarides.com/blog/2019-08-26-decompress-the-new-decompress-api> [performance improvements] <https://tarides.com/blog/2019-09-13-decompress-experiences-with-ocaml-optimization> Other OCaml News ════════════════ From the ocamlcore planet blog ────────────────────────────── Here are links from many OCaml blogs aggregated at [OCaml Planet]. • [How We Lost at The Delphi Oracle Challenge] • [Tarides sponsors the Oxbridge Women in Computer Science Conference 2020] • [Coq 8.12.2 is out] • [First release of MetAcsl plugin] • [Announcing MirageOS 3.10] • [ ReScript 8.4] • [Coq 8.13+beta1 is out] [OCaml Planet] <http://ocaml.org/community/planet/> [How We Lost at The Delphi Oracle Challenge] <https://seb.mondet.org/b/0010-delphi-challenge-post-vivum.html> [Tarides sponsors the Oxbridge Women in Computer Science Conference 2020] <https://tarides.com/blog/2020-12-14-tarides-sponsors-the-oxbridge-women-in-computer-science-conference-2020> [Coq 8.12.2 is out] <https://coq.inria.fr/news/coq-8-12-2-is-out.html> [First release of MetAcsl plugin] <https://frama-c.com/fc-plugins/metacsl.html> [Announcing MirageOS 3.10] <https://mirage.io/blog/announcing-mirage-310-release> [ ReScript 8.4] <https://rescript-lang.org/blog/bucklescript-release-8-4> [Coq 8.13+beta1 is out] <https://coq.inria.fr/news/coq-8-13beta1-is-out.html> Old CWN ═══════ If you happen to miss a CWN, you can [send me a message] and I'll mail it to you, or go take a look at [the archive] or the [RSS feed of the archives]. If you also wish to receive it every week by mail, you may subscribe [online]. [Alan Schmitt] [send me a message] <mailto:email@example.com> [the archive] <http://alan.petitepomme.net/cwn/> [RSS feed of the archives] <http://alan.petitepomme.net/cwn/cwn.rss> [online] <http://lists.idyll.org/listinfo/caml-news-weekly/> [Alan Schmitt] <http://alan.petitepomme.net/> [-- Attachment #2: Type: text/html, Size: 32830 bytes --]
next reply other threads:[~2021-01-12 9:47 UTC|newest] Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-12 9:47 Alan Schmitt [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-05-24 8:04 Alan Schmitt 2022-05-17 7:12 Alan Schmitt 2022-05-10 12:30 Alan Schmitt 2022-05-03 9:11 Alan Schmitt 2022-04-26 6:44 Alan Schmitt 2022-04-19 5:34 Alan Schmitt 2022-04-12 8:10 Alan Schmitt 2022-04-05 11:50 Alan Schmitt 2022-03-29 7:42 Alan Schmitt 2022-03-22 13:01 Alan Schmitt 2022-03-15 9:59 Alan Schmitt 2022-03-01 13:54 Alan Schmitt 2022-02-22 12:43 Alan Schmitt 2022-02-08 13:16 Alan Schmitt 2022-02-01 13:00 Alan Schmitt 2022-01-25 12:44 Alan Schmitt 2022-01-11 8:20 Alan Schmitt 2022-01-04 7:56 Alan Schmitt 2021-12-28 8:59 Alan Schmitt 2021-12-21 9:11 Alan Schmitt 2021-12-14 11:02 Alan Schmitt 2021-11-30 10:51 Alan Schmitt 2021-11-16 8:41 Alan Schmitt 2021-11-09 10:08 Alan Schmitt 2021-11-02 8:50 Alan Schmitt 2021-10-19 8:23 Alan Schmitt 2021-09-28 6:37 Alan Schmitt 2021-09-21 9:09 Alan Schmitt 2021-09-07 13:23 Alan Schmitt 2021-08-24 13:44 Alan Schmitt 2021-08-17 6:24 Alan Schmitt 2021-08-10 16:47 Alan Schmitt 2021-07-27 8:54 Alan Schmitt 2021-07-20 12:58 Alan Schmitt 2021-07-06 12:33 Alan Schmitt 2021-06-29 12:24 Alan Schmitt 2021-06-22 9:04 Alan Schmitt 2021-06-01 9:23 Alan Schmitt 2021-05-25 7:30 Alan Schmitt 2021-05-11 14:47 Alan Schmitt 2021-05-04 8:57 Alan Schmitt 2021-04-27 14:26 Alan Schmitt 2021-04-20 9:07 Alan Schmitt 2021-04-06 9:42 Alan Schmitt 2021-03-30 14:55 Alan Schmitt 2021-03-23 9:05 Alan Schmitt 2021-03-16 10:31 Alan Schmitt 2021-03-09 10:58 Alan Schmitt 2021-02-23 9:51 Alan Schmitt 2021-02-16 13:53 Alan Schmitt 2021-02-02 13:56 Alan Schmitt 2021-01-26 13:25 Alan Schmitt 2021-01-19 14:28 Alan Schmitt 2021-01-05 11:22 Alan Schmitt 2020-12-29 9:59 Alan Schmitt 2020-12-22 8:48 Alan Schmitt 2020-12-15 9:51 Alan Schmitt 2020-12-01 8:54 Alan Schmitt 2020-11-03 15:15 Alan Schmitt 2020-10-27 8:43 Alan Schmitt 2020-10-20 8:15 Alan Schmitt 2020-10-06 7:22 Alan Schmitt 2020-09-29 7:02 Alan Schmitt 2020-09-22 7:27 Alan Schmitt 2020-09-08 13:11 Alan Schmitt 2020-09-01 7:55 Alan Schmitt 2020-08-18 7:25 Alan Schmitt 2020-07-28 16:57 Alan Schmitt 2020-07-21 14:42 Alan Schmitt 2020-07-14 9:54 Alan Schmitt 2020-07-07 10:04 Alan Schmitt 2020-06-30 7:00 Alan Schmitt 2020-06-16 8:36 Alan Schmitt 2020-06-09 8:28 Alan Schmitt 2020-05-19 9:52 Alan Schmitt 2020-05-12 7:45 Alan Schmitt 2020-05-05 7:45 Alan Schmitt 2020-04-28 12:44 Alan Schmitt 2020-04-21 8:58 Alan Schmitt 2020-04-14 7:28 Alan Schmitt 2020-04-07 7:51 Alan Schmitt 2020-03-31 9:54 Alan Schmitt 2020-03-24 9:31 Alan Schmitt 2020-03-17 11:04 Alan Schmitt 2020-03-10 14:28 Alan Schmitt 2020-03-03 8:00 Alan Schmitt 2020-02-25 8:51 Alan Schmitt 2020-02-18 8:18 Alan Schmitt 2020-02-04 8:47 Alan Schmitt 2020-01-28 10:53 Alan Schmitt 2020-01-21 14:08 Alan Schmitt 2020-01-14 14:16 Alan Schmitt 2020-01-07 13:43 Alan Schmitt 2019-12-31 9:18 Alan Schmitt 2019-12-17 8:52 Alan Schmitt 2019-12-10 8:21 Alan Schmitt 2019-12-03 15:42 Alan Schmitt 2019-11-26 8:33 Alan Schmitt 2019-11-12 13:21 Alan Schmitt 2019-11-05 6:55 Alan Schmitt 2019-10-15 7:28 Alan Schmitt 2019-09-03 7:35 Alan Schmitt
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [Caml-list] Attn: Development Editor, Latest OCaml Weekly News' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).