News for hackers. Stuff that matters.

A comment on The Unison language. Parent comment

Re:The Unison language by breuleux on Friday January 10, 2020 @05:15PM (#22016206)
> The most hopeful case is that there is ONE place that isn't 'strictly append only', and that's, for lack of a better term, the 'main pointer'. Which hash is the actual state of the app as it should be compiled and deployed right now?

I think that's how it works. The way I understand it from reading the tour, there is a separate store for the code and for the name mappings. Both main functions would merge without conflict into the code store, but the mappings would conflict.

[ Parent | on HN ]
Re:The Unison language by jayrhynas on Friday January 10, 2020 @05:28PM (#22016296)
This [1] seems to be the "head pointer", and I assume it would conflict when merging. In fact, would it not conflict on every merge even if unrelated code was changed, since it hashes on the value of the entire codebase?

Edit: After thinking some more, it wouldn't conflict on a file-level, since the file itself has a different name. But there would be now two files in the _head folder, and I assume the `ucm` tool would detect that and present the user with merging options?

[1]: https://git.io/Jvfen

[ Parent | on HN ]