rohanat

7 ms·

1. 1.▲
   by rohanat 3mo ago

   have you considered a deterministic tier before the embedding pass? I feel that approach can be more efficient.
2. 2.▲
   by rohanat 3mo ago

   https://ataraxy-labs.github.io/weave/learn.html
3. 3.▲
   by rohanat 3mo ago

   This is great, and sorry we never landed a time after Reddit, that one's on me. Let's actually fix it, could you email me on rohan@ataraxy-labs.com. For context on where the gap might be: weave matches at the entity level (functio
4. 4.▲
   by rohanat 3mo ago

   Different layer. SemanticDiff is a language-aware diff viewer, it helps you read a change. weave is a merge driver, it resolves the three-way merge so you get fewer conflicts in the first place. The closer analog to SemanticDiff in our stac
5. 5.▲
   by rohanat 3mo ago

   I am sorry about your experience igra, but to be fair, yeah there are some failure cases but I love to receive any feedback that you think can improve it and make it a more generalized solution.
6. 6.▲
   by rohanat 3mo ago

   Thanks a lot for the feedback, appreicate it!
7. 7.▲
   by rohanat 3mo ago

   Yeah you can find the readme on the github repository.
8. 8.▲
   by rohanat 3mo ago

   Thanks a lot for this feedback, you are right, but I actually had a page about the merge algorithm more in depth, maybe you will love it.
9. 9.▲
   by rohanat 3mo ago

   Totally fair. The merge logic doesn't care whether a human or an agent wrote the commit, "two commits touch different functions in the same file, clean merge" is exactly how a human should read it too. We lead with agents bec
10. 10.▲
    by rohanat 3mo ago

    Good question. Weave is a standard git merge driver, so it slots into the existing flow rather than replacing it. You wire it up in .gitattributes, and it only changes the 3-way conflict-resolution step that git already runs. The output is
11. 11.▲
    Weave: Merging based on language structure and not lines(ataraxy-labs.github.io)

    68 points by rohanat 3mo ago|46 comments