3 ms·
What comes next, IMO, is semantic version control. Version control that is aware of changes not at the file and line level, but at the function level, the modu
by Slackwise 6y ago
What comes next, IMO, is semantic version control.
Version control that is aware of changes not at the file and line level, but at the function level, the module level, the library level, the language-specific construct level.
(Rich Hickey, creator of Clojure, played around with this idea, but I'm not sure where it went.)
- gnufx 6y agoDarcs should be able to support semantic patches, but currently the only alternative patch type is token replacement. How useful semantics might be in a project with N different components' semantics, I don't know.
- IshKebab 6y agoThere's a project that does diffs on Javascript at the AST level rather than the line level. I haven't tried it though and it is only for resolving conflicts.
- harperlee 6y agoHe is referring to codeq: https://github.com/Datomic/codeq https://github.com/Datomic/codeq which has a last commit on 2014. But there have been recent rumours (https://medium.com/@sfyire/can-codeq-2-solve-clojures-weaknesses-dd8312ea7add https://medium.com/@sfyire/can-codeq-2-solve-clojures-weakne...) that Hickey is working in a new version of it. Fingers crossed!