Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Weave – A language aware merge algorithm based on entities

github.com

Post reply on HN
Print view View original

41–50 of 123 posts

Re: Weave – A language aware merge algorithm based on entities

#41

Post by gritzko »

rs545837 wrote: post #40
gritzko wrote: post #34

Earlier quoted context omitted.

This will not work for refactors. In fact, any other change will break the hash. I know because I used this approach for quite some time.

Thanks a lot, I will test it out as you said, in the mean time, could you also open up an issue on the repo, so that it helps me and others to track the issue.

I will ask Claude to open it, thanks!

Re: Weave – A language aware merge algorithm based on entities

#42

Post by rs545837 »

pfdietz wrote: post #35
gritzko wrote: post #12

At this point, the question is: why keep files as blobs in the first place. If a revision control system stores AST trees instead, all the work is AST-level. One can run SQL-level queries then to see what is changing where. Like - do any concurrent branches touch this function? - what new uses did this function accrete recently? - did we create any actual merge conflicts? Almost LSP-level querying, involving versions…

Well, if you're programming in C or C++, there may not be a parse tree. Tree-sitter makes a best effort attempt to parse but it can't in general due to the preprocessor.

Great point. C/C++ with macros and preprocessor directives is where tree-sitter's error recovery gets stretched. We support both C and C++ in sem-core(https://github.com/Ataraxy-Labs/sem) but the entity extraction is best-effort for heavily macro'd code. For most application-level C++ it works well, but something like the Linux kernel would be rough. Honestly that's an argument for gritzko's AST-native storage approach where the parser can be more tightly integrated.

Re: Weave – A language aware merge algorithm based on entities

#43

Post by Palanikannan »

deckar01 wrote: post #28
rs545837 wrote: post #25

Earlier quoted context omitted.

What do you mean?

It’s your GitHub profile. It looks suspiciously just like the other 10 GitHub users that have been spamming AI generated issues and PRs for the last 2 weeks. They always go quiet eventually. I suspect because they are violating GitHub’s ToS, but maybe they just run out of free tokens.

https://github.com/Ataraxy-Labs/weave/pull/11

Dude did you just call me AI generated haha, i've been actively using weave for a gui I've been building for blazingly fast diffs

https://x.com/Palanikannan_M/status/2022190215021126004

So whenever I run into bugs I patched locally in my clone, I try to let the clanker raise a pr upstream, insane how easy things are now.

Re: Weave – A language aware merge algorithm based on entities

#44

Post by rs545837 »

handfuloflight wrote: post #38
gritzko wrote: post #12

At this point, the question is: why keep files as blobs in the first place. If a revision control system stores AST trees instead, all the work is AST-level. One can run SQL-level queries then to see what is changing where. Like - do any concurrent branches touch this function? - what new uses did this function accrete recently? - did we create any actual merge conflicts? Almost LSP-level querying, involving versions…

Well, I'll be diving in. Thank you for sharing. Same for Weave.

Awesome, let me know how it goes. Happy to help if you hit any rough edges.

Re: Weave – A language aware merge algorithm based on entities

#45

Post by rs545837 »

gritzko wrote: post #41
rs545837 wrote: post #40

Earlier quoted context omitted.

Thanks a lot, I will test it out as you said, in the mean time, could you also open up an issue on the repo, so that it helps me and others to track the issue.

I will ask Claude to open it, thanks!

Thanks, lemme know how it goes, I will review and we can discuss over the issue.

Re: Weave – A language aware merge algorithm based on entities

#46

Post by deckar01 »

Palanikannan wrote: post #43
deckar01 wrote: post #28

Earlier quoted context omitted.

It’s your GitHub profile. It looks suspiciously just like the other 10 GitHub users that have been spamming AI generated issues and PRs for the last 2 weeks. They always go quiet eventually. I suspect because they are violating GitHub’s ToS, but maybe they just run out of free tokens.

https://github.com/Ataraxy-Labs/weave/pull/11 Dude did you just call me AI generated haha, i've been actively using weave for a gui I've been building for blazingly fast diffs https://x.com/Palanikannan_M/status/2022190215021126004 So whenever I run into bugs I patched locally in my clone, I try to let the clanker raise a pr upstream, insane how easy things are now.

[flagged]

Re: Weave – A language aware merge algorithm based on entities

#48

Post by rs545837 »

deckar01 wrote: post #39
rs545837 wrote: post #36

Earlier quoted context omitted.

Thanks again for criticising, so tackling each of your comment: GitHub’s ToS, because you suspect, so I can help you understand them. > What violates it: 1. Automated Bulk issues/PRs, that we don't own 2. Fake Stars or Engagement Farming 3. Using Bot Accounts. We own the repo, there's not even a single fake star, I don't even know how to create a bot account lol. > Scenario when we run out of free tokens. Open AI and…

And you are opening issues on projects trying to get them to adopt your product. Seems like spam to me. How much are you willing to spend maintaining this project if those free tokens go away?

When you're just a normal guy genuinely trying to build something great and there's nobody who believes in you yet, the only thing you can do is go to projects you admire and ask "would this help you?" Patrick Collison did the same thing early on, literally taking people's laptops to install Stripe.
Post reply on HN