Gabriel Scherer

The blocking factor (to me) appears to be to find a maintainer willing to review this change. The maintainers that are typically interested in multicore aspects of the runtime are...

Using a submodule of `Thread` forces to link the thread runtime. This may not be what library-authors want if they want to write code that is thread-safe, but without deciding...

In #13922, @NicholasLYang has expressed interest in contributing to this work. @Octachron, do you know how to vocalize your plans in a way that makes it possible for others to...

> With this patch, all regular atomic writes now incur an additional integer untagging operation. [..] It is probably true for most (all?) hardware and workflows, especially given that this...

My appetite for syntax dicussions is fairly low. Maybe we could first consider the feature and its implementation, merge the present PR if we decide to go for it, and...

This morning I gave a talk on The Pattern-Matching Bug, and we realized (discussion with @clef-men and @fpottier) that there is a connection to atomic record fields: 1. This PR...

I guess it doesn't help that we were discussing The Pattern-Matching Bug at the same time, whose longer name could be What Can Go Horribly Wrong If You Pattern-Match On...

The osx-arm64 fails due to a difference in cmm stamps (I'm not sure why an architecture has different stamps from the other, but oh well). We fixed previous such failures...

A proposal for a Changes entry: ``` - RFCs#39, #13404: atomic record fields (Clément Allain and Gabriel Scherer, review by KC Sivaramakrishnan, Basile Clément and Olivier Nicole) ```

Consensus from the maintainer meeting: mild consensus in favor of the feature. People wondered about whether the current proposal (where the record value and the offset are packed together in...