4 ms·
All version control tools have the same problem since AFAIK none of them care about the semantics of the program being version-controlled (except Unison). For
by magnio 3y ago
All version control tools have the same problem since AFAIK none of them care about the semantics of the program being version-controlled (except Unison).
For example, in file foo.js you export the function foo. Now, if you delete the function foo, while your colleague import it into bar.js, the resultant changes are consistent, but the program is now functionally broken.
- riffraff 3y agomonticello[0] cares about semantics too! Tho I guess it cheats existing in an image-based world (I have never used it, it's just something stuck in my memory from many years ago). [0] https://wiki.squeak.org/squeak/1287 https://wiki.squeak.org/squeak/1287
- gmueckl 3y agoPlsstic's diff tool is also centered around syntactic units of the programming language rather than stupidly scanning for line breaks, if it recognizes the language.
- IshKebab 3y agoThat still wouldn't mean that the merge is semantically correct.
- skybrian 3y agoThis is why we test our builds using continuous integration. Only updates that compile and pass the tests should be published. How does Pijul handle continuous integration? If there’s nothing interesting going on with that then I don’t see how the UX can be any different for publishing new versions.