Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Very impressive enhancement. Not a panacea though. It uses tree-sitter approach to solve situations when two users change the same line of code. For example one change function name and other adds a new argument. It will merge it without conflicts. It still has some troubles to solve complex issues, without knowing author intensions. But can significantly simplify developers' lives. Not sure if it would land into git very soon. It requires all git to know all the parsers you need. But definitely worth adding.


This is a seprate tool that one can tell git to use.


What does it do, when the change in function name mean that the number of spaces before each parameter (alignment) changed?


If one of developers changed function name and the other changes alignment of parameters in the same line, this tool would recognize the changes and merge this line without conflicts. Regular git algorithm would turn it into a conflict because the changes happened on the same line


The idea is that the alignment and function name change happens on the same side, since the alignment is caused by the function name. The other side e.g. adds another parameter. Does the new parameter get the correct alignment, or that of the old function name?


It would be merged into a valid code. What's about alignment in particular, I'm not sure




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: