Linearity still forces one to have a mutex for updating the head position, no? Although with good design it can scale up very well (out, that’s harder)
(Also rebases lie about what was tested, but fortunately nobody ever reads history to see those lies)
Yes. The goal of the Bonsai data model is to make that critical section as small, and involve as few pointer chases, as possible.
Agreed that push rebases don’t detect semantic merge conflicts across files (they worked at the file and directory level). In massive monorepos this isn’t a major problem though, especially because work would generally be done against the latest “warm” bookmark, which meant a bookmark for which the build system had already verified things and cached build results.
Linearity still forces one to have a mutex for updating the head position, no? Although with good design it can scale up very well (out, that’s harder)
(Also rebases lie about what was tested, but fortunately nobody ever reads history to see those lies)
score 1 · canonical
Yes. The goal of the Bonsai data model is to make that critical section as small, and involve as few pointer chases, as possible.
Agreed that push rebases don’t detect semantic merge conflicts across files (they worked at the file and directory level). In massive monorepos this isn’t a major problem though, especially because work would generally be done against the latest “warm” bookmark, which meant a bookmark for which the build system had already verified things and cached build results.
score 1 · canonical