Antonin Décimo comments

Results 287 comments of


                                            Antonin Décimo

Let CI's sanitizer job use clang's default version

#13290 will also modify the script. I think this PR should be merged before. I don't see anything holding it back.

Update the CI and deployment to OCaml 5.2.1, Alpine 2.21, opam 2.3, and use BuildKit syntax in the Dockerfile

Yes, BuildKit needs to be enabled in ocurrent-deployer for ocaml.org. Regardless, are you interested in these changes?

Update the CI and deployment to OCaml 5.2.1, Alpine 2.21, opam 2.3, and use BuildKit syntax in the Dockerfile

ping! The deployer has learned to use BuildKit, and the Alpine 3.21 image has been released.

Update the CI and deployment to OCaml 5.2.1, Alpine 2.21, opam 2.3, and use BuildKit syntax in the Dockerfile

_ping_

Update the CI and deployment to OCaml 5.2.1, Alpine 2.21, opam 2.3, and use BuildKit syntax in the Dockerfile

Superseded by #3281.

gcc: fix partial linking by using gcc -r instead of ld -r

The PR seems sound. I just wonder if there's a better fix in the general case. I tried to get a better understanding of how a user might select a...

runtime: distinguish two kind of mutexes

> use correctly for non-experts such as myself Speaking as a non-expert myself, I often have to remind myself that blocking/non-blocking in this context refers to the domain lock and...

runtime: distinguish two kind of mutexes

Perhaps Clang's [Thread Safety Analysis](https://clang.llvm.org/docs/ThreadSafetyAnalysis.html) static annotations could help and ensure each access is correctly paired with the right kind of mutex.

Use more POSIX thread-safe functions in libunix

Thanks for the review. I've applied your suggestions, and also added a change to use `getlogin_r`.

Add a chapter on native debugger to the manual.

Could you perhaps replace the `5.4.0` strings with a variable such that the document stays in sync with the current version of OCaml? Or use a version-agnostic switch name such...