OCaml on Github (bot)

A Service created on 2024/03/27.

Bot following events on OCaml Github and publishing some of them.

I watch the following Gitlab forges to signal new projects with OCaml as programming language:

Not continuously running

Has 13 followers. Follows 1 actor.

Most recent Create activities

tmcgilchrist commented on issue 12979: "MacOS: bad install names for shared libs (libasmrun_shared.so etc.)"

Please keep this open. It is relevant to obazl and possibly future debugging support. On Mon, 17 Mar 2025 at 3:25 pm, github-actions[bot] < ***@***.***> wrote: > This issue has been open one...

https://github.com/.../12979#issuecomment-2728096945

github-actions[bot] commented on issue 12979: "MacOS: bad install names for shared libs (libasmrun_shared.so etc.)"

This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more com...

https://github.com/.../12979#issuecomment-2728091762

New #ocaml project ilan dahmane / robot_projet

New #ocaml project ilan dahmane / Dpll

tmcgilchrist commented on issue 13876: "Document Printexc gotchas"

The two location you want to change to add the hint about using `ocamlc -g` would be: ``` File: runtime/backtrace.c 82:15: info = "Called from"; File: stdlib/printexc.ml 146:64: if po...

https://github.com/.../13876#issuecomment-2727716621

SkySkimmer commented on issue 13377: "Primitive aliases (RFC #44)"

>Question: a natural extension of the language would be to allow let-binding in signatures, restricted to a name or a value. Reusing `let` opens questions we may not want to bother with. For instan...

https://github.com/.../13377#issuecomment-2727483655

gasche commented on issue 13377: "Primitive aliases (RFC #44)"

Question: a natural extension of the language would be to allow `let`-binding in signatures, restricted to a name or a value. ```ocaml module _ : sig type t let int_of_t : t -> t = Fun.id e...

https://github.com/.../13377#issuecomment-2727224094

gasche commented on issue 13770: "Change escaping rules for inline record types"

Atomic record operations are polymorphic in the type of the record value. The PR lets me type-check `ignore r` or `ignore (Fun.id r)`, and similarly it should let me type-check `Atomic.Field.get r [%a...

https://github.com/.../13770#issuecomment-2727221158

garrigue commented on issue 13872: "improve "Their kinds differ" error message"

I do not know about whether there is a "good" reason. I suppose this coincides with the theory @xavierleroy implemented. Morally, the idea is that a concrete type definition does two things: it define...

https://github.com/.../13872#issuecomment-2727194011

garrigue commented on issue 13770: "Change escaping rules for inline record types"

I agree that restricting only the scope in patterns is similar in intuition to existential types, and is probably easy to understand for users. I am still curious of the plan for atomic record field ...

https://github.com/.../13770#issuecomment-2727190455

New #ocaml project Dubois / why3_ sparsesubsets

c-cube commented on issue 13870: "add `Thread.set_extended_uncaught_exception_handler`"

On March 15, 2025 9:48:40 AM EDT, Gabriel Scherer ***@***.***> wrote: >gasche left a comment (ocaml/ocaml#13870) > >If you have the problem right now, could you try just calling `Printexc.get_r...

https://github.com/.../13870#issuecomment-2726577801

gasche commented on issue 13870: "add `Thread.set_extended_uncaught_exception_handler`"

If you have the problem right now, could you try just calling `Printexc.get_raw_backtrace ()` from the uncaught exception handler to get the uncaught exception backtrace? > Right now to get a backt...

https://github.com/.../13870#issuecomment-2726569777

dbuenzli commented on issue 13870: "add `Thread.set_extended_uncaught_exception_handler`"

Yes a very good quote. Here's another one: > Is there an actual design that I failed to see here ? From an end-user perspective I find all that quite confusing, are we going to need to set multiple...

https://github.com/.../13870#issuecomment-2726547509

c-cube commented on issue 13870: "add `Thread.set_extended_uncaught_exception_handler`"

Quoting yourself from that thread: > Not sure what the objection is here. Such callbacks already need to exist anyways. They are not meant to be used they are here as a last resort mecanism so that n...

https://github.com/.../13870#issuecomment-2726539228

nojb commented on issue 13720: "Add Result.{get_ok',error_to_failure}"

I agree we have reached a point where it is up for the core devs to make a call. In [a comment](https://github.com/ocaml/ocaml/pull/13696#issuecomment-2568990231) in #13696 @gasche did not seem strong...

https://github.com/.../13720#issuecomment-2726479971

dbuenzli commented on issue 13870: "add `Thread.set_extended_uncaught_exception_handler`"

This feels like adding more to an already badly designed system. Wouldn't that be an opportunity to finally design something sensitive and solve https://github.com/ocaml/ocaml/issues/11074 ?

https://github.com/.../13870#issuecomment-2726375100

dbuenzli commented on issue 13696: "Add Result.product and Result.Syntax"

This is also part of the plan of getting rid of my tiny and annoying to carry `Result` module overlay after 5.4 :-) It has been two months now and I think a decision should be taken on that one, ei...

https://github.com/.../13696#issuecomment-2726371005

dbuenzli commented on issue 13720: "Add Result.{get_ok',error_to_failure}"

Two months later. I'd really like to get rid of my *extremely tiny* and thus *extremely* annoying to carry, `Result` module overlay after `5.4` and this is part of the plan. Here are a few possibi...

https://github.com/.../13720#issuecomment-2726361129

Next