[Caml-list] Attn: Development Editor, Latest OCaml Weekly News

[Alan Schmitt <alan.schmitt@polytechnique.org>]

[-- Attachment #1: Type: text/plain, Size: 11512 bytes --]

Hello

Here is the latest OCaml Weekly News, for the week of August 27 to
September 03, 2024.

Table of Contents
─────────────────

ppx_minidebug 2.0: verbosity levels
Ppx by example - repo to help on ppx learning
Blog Post: Simple Example where Ocaml calls a C function
Outreachy December 2024 Round
Other OCaml News
Old CWN


ppx_minidebug 2.0: verbosity levels
═══════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ann-ppx-minidebug-2-0-verbosity-levels/15212/1>


Lukasz Stafiniak announced
──────────────────────────

  I'm pleased to mention that [ppx_minidebug 2.0] is available now. The
  README at [ppx_minidebug - GitHub] is the user manual, and the runtime
  API is documented here: [ppx_minidebug.Minidebug_runtime].

  Version 2.0 brings linear verbosity log levels. Both logging scopes
  and individual log statements can be either: at a default (omitted)
  log level, at a compile-time log level (e.g. `[%log2 "test"]' logs
  `test' at level 2), or at a runtime-provided log level (e.g. `[%logN
  for_level; "test"]' logs `test' at level `for_level'). When the level
  to log at is omitted, it is inherited from its direct syntactic
  logging scope (i.e. the log entry that the log or log entry is
  syntactically in – not the log entry that the log is dynamically
  attached to, if it's different). Providing a compile-time log level
  will prune the generated code accordingly. See more here:
  [ppx_minidebug: Using as a logging framework].

  Version 1.6 brought support for local runtimes, where the runtime for
  logging in a logging scope is fetched by a user-provided function. The
  function can for example use domain-local storage. See more here:
  [ppx_minidebug: Dealing with concurrent execution].

  Happy debugging!


[ppx_minidebug 2.0] <https://github.com/lukstafi/ppx_minidebug>

[ppx_minidebug - GitHub] <https://github.com/lukstafi/ppx_minidebug>

[ppx_minidebug.Minidebug_runtime]
<https://lukstafi.github.io/ppx_minidebug/ppx_minidebug/Minidebug_runtime/index.html>

[ppx_minidebug: Using as a logging framework]
<https://github.com/lukstafi/ppx_minidebug?tab=readme-ov-file#using-as-a-logging-framework>

[ppx_minidebug: Dealing with concurrent execution]
<https://github.com/lukstafi/ppx_minidebug?tab=readme-ov-file#dealing-with-concurrent-execution>


Ppx by example - repo to help on ppx learning
═════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/ppx-by-example-repo-to-help-on-ppx-learning/15213/1>


Pedro Braga announced
─────────────────────

  Over the past few weeks, I've started my journey to learn PPX, and
  during this process, I found it challenging to find examples. So, I
  began creating my own examples and adding explanations for myself.

  I realized that I could make my examples and explanations public
  because this would push me to learn more deeply (as I’d need to
  provide better and clearer explanations) and could also help anyone
  else on this learning path. @davesnx also encouraged me to share my
  process (maybe through a blog post in the future). So, I created this
  repository: [github.com/pedrobslisboa/ppx-by-example].

  The idea is to have examples and an explanation for each detail on
  those. It has also a brief explanation about the subject on every
  README.

  I have a few notes:
  • It is a wip project, which means that there are parts in
    development. But sharing it is also a way to push me to improve this
    project.
  • As I said, I'm on the process of learning PPX, so probably I missed
    or added something wrongly, so please If you notice it, share it on
    the repo so I can fix.
  • I am also in the process of learning OCaml. I started coding in
    OCaml this year (professionally just last month), so this repository
    might not have the best code. If you think it can be improved,
    please let me know. :heart:
  • I'm not a native English speaker or the best writer. I asked ChatGPT
    to help fix some mistakes and improve cohesion, but if you notice
    anything that needs to be improved, please let me know. :heart:

  Besides that, any comments, help, or additions are welcome. I hope
  this can be helpful :3 Thank you all!


[github.com/pedrobslisboa/ppx-by-example]
<https://github.com/pedrobslisboa/ppx-by-example>


Blog Post: Simple Example where Ocaml calls a C function
════════════════════════════════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/blog-post-simple-example-where-ocaml-calls-a-c-function/15211/3>


Deep in this thread, Tim McGilchrist said
─────────────────────────────────────────

  My favourite example at the moment is this one from [Retrofitting
  Effect Handlers onto OCaml]. It shows OCaml calling C, C calling an
  OCaml callback and exceptions crossing those boundaries.

  ┌────
  │ $ cat meander.ml
  └────

  ┌────
  │ external ocaml_to_c
  │          : unit -> int = "ocaml_to_c"
  │ exception E1
  │ exception E2
  │ let c_to_ocaml () = raise E1
  │ let _ = Callback.register
  │           "c_to_ocaml" c_to_ocaml
  │ let omain () =
  │   try (* h1 *)
  │     try (* h2 *) ocaml_to_c ()
  │     with E2 -> 0
  │   with E1 -> 42
  │ let _ = assert (omain () = 42)
  └────

  ┌────
  │ $ cat meander_c.c
  └────

  ┌────
  │ #include <caml/mlvalues.h>
  │ #include <caml/callback.h>
  │ 
  │ value ocaml_to_c (value unit) {
  │     caml_callback(*caml_named_value
  │                   ("c_to_ocaml"), Val_unit);
  │     return Val_int(0);
  │ }
  └────

  Compile it with OCaml 5.2:

  ┌────
  │ $ ocamlopt --version
  │ 5.2.0
  │ $ ocamlopt meander_c.c meander.ml -o meander.exe
  │ $ ./meander.exe
  │ $ echo $?
  │ 0
  └────

  Bonus you can use GDB/LLDB on this to set breakpoints in both OCaml
  and C.


[Retrofitting Effect Handlers onto OCaml]
<https://doi.org/10.1145/3453483.3454039>


Outreachy December 2024 Round
═════════════════════════════

  Archive:
  <https://discuss.ocaml.org/t/outreachy-december-2024-round/15223/1>


Patrick Ferris announced
────────────────────────

  With the conclusion of the previous Outreachy round (see [Outreachy
  Demo Presentation]), the next round is fast approaching and the OCaml
  community has signed up again to participate!


[Outreachy Demo Presentation]
<https://discuss.ocaml.org/t/outreachy-demo-presentation/15189>

The Next Round
╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  The *deadline for mentors to [submit a project] is [date=2024-09-11
  timezone="Europe/London"]*. If people are interested in mentoring and
  they maintain an open-source project, then they can reach out directly
  to me and I can help scope a project, explain the contribution period
  and provide as much other help as we can! Co-mentoring is also an
  option for people who are interested in mentoring but do not have a
  specific project – do reply to this thread if that's you!

  When signing up mentors propose an open-source project where
  prospective interns submit PRs during the “contribution phases” as
  part of their application. Mentors will then choose an intern to work
  with for 3 months. A more detailed explanation is available [on the
  Outreachy mentor section ].

  I'm particularly interested in *projects from some of the larger OCaml
  projects* (e.g. dune, opam, ppxlib, miou, eio, cohttp, melange
  etc.). I'm very happy to help with co-mentoring on any of these
  projects. If you are interested and are a maintainer of a larger
  project, please do reach out. Of course, smaller projects are still
  very much possible.


[submit a project] <https://www.outreachy.org/communities/cfp/ocaml/>

[on the Outreachy mentor section ]
<https://www.outreachy.org/mentor/#mentor>


Funding
╌╌╌╌╌╌╌

  _Funding for this upcoming Outreachy round is not yet finalised_. We
  hope to have funding for three interns, I will reply to this thread
  once things are confirmed which should be soon. If any company is
  interested in supporting the OCaml community Outreachy initative
  please do reach out to me.

  I'd also like to take this moment to raise some awareness for the
  current [struggles Outreachy is facing]. The OCaml community has
  benefited massively from Outreachy. Both by participating directly as
  a community (see <https://ocaml.org/outreachy> for some past projects)
  and via the participation of other communities. I'm very grateful for
  everyone who has taken part in some way, including non-mentors
  engaging with the interns.

  As always if you have any general questions or mentoring ideas do
  comment on this thread or reach out directly.

  Thanks!


[struggles Outreachy is facing]
<https://www.outreachy.org/blog/2024-08-14/outreachy-needs-your-help/>


Other OCaml News
════════════════

>From the ocaml.org blog
───────────────────────

  Here are links from many OCaml blogs aggregated at [the ocaml.org
  blog].

  • [The Biggest Functional Programming Conference of the Year: What are
    we Bringing to ICFP?]
  • [ICFP 2024]
  • [Project-Wide Occurrences: A New Navigation Feature for OCaml 5.2
    Users]
  • [What the interns have wrought, 2024 edition]


[the ocaml.org blog] <https://ocaml.org/blog/>

[The Biggest Functional Programming Conference of the Year: What are we
Bringing to ICFP?]
<https://tarides.com/blog/2024-08-30-the-biggest-functional-programming-conference-of-the-year-what-are-we-bringing-to-icfp>

[ICFP 2024] <https://blog.janestreet.com/icfp-2024-index/>

[Project-Wide Occurrences: A New Navigation Feature for OCaml 5.2 Users]
<https://tarides.com/blog/2024-08-28-project-wide-occurrences-a-new-navigation-feature-for-ocaml-5-2-users>

[What the interns have wrought, 2024 edition]
<https://blog.janestreet.com/what-the-interns-have-wrought-2024-edition-index/>


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
  to the [caml-list].

  [Alan Schmitt]


[send me a message] <mailto:alan.schmitt@polytechnique.org>

[the archive] <https://alan.petitepomme.net/cwn/>

[RSS feed of the archives] <https://alan.petitepomme.net/cwn/cwn.rss>

[caml-list] <https://sympa.inria.fr/sympa/info/caml-list>

[Alan Schmitt] <https://alan.petitepomme.net/>


[-- Attachment #2: Type: text/html, Size: 23041 bytes --]