arxanas

8 ms·

31.
by arxanas 3y ago
> it's not clear to me if the order matters and how many can be listed It's worth noting that in Git, 1) the order is recorded and tracked in the commit (but almost always doesn't matter), and 2) you can have any number
32.
by arxanas 3y ago
Support/discussion happens a fair amount on GitHub Discussions and Issues as well.
33.
by arxanas 3y ago
> Not until I run some jj command? It's kind of begging for a 'jjd' isn't it? Or if you use an IDE you'd want/need it to be not just saving but doing some kind of 'jj nop'. In practice, I find that
34.
by arxanas 3y ago
> jj merge exists but it's not obvious which revisions you are supposed to pass to it I don't think I understand your confusion. `jj merge` is essentially like Git merge, except that you also normally pass the current commit as
35.
by arxanas 3y ago
There is a little more detail here: https://github.com/martinvonz/jj/blob/main/docs/technical/co... Storing the conflicts symbolically in this way lets you reproduce the conflicts later and eve
36.
by arxanas 3y ago
> I wonder how this behave if commits get randomly pushed to origin You would expect the push to fail in the normal way, as if you had manually done the rebase, because your commit history may have diverged. That being said, I don't
37.
by arxanas 3y ago
It's not really different than using Git to work on the same branch. If you and the teammate commit to the same branch, then you'll need to resolve the divergence somehow, usually a merge or rebase, or choose to forcibly overwrite
38.
by arxanas 3y ago
The `Backend` interface is not that wide: https://github.com/martinvonz/jj/blob/48b1a1c533f16fc5df5269... . Mostly it just handles reading/writing various objects. You could very plausibly add IPFS suppor
39.
by arxanas 3y ago
I don't understand why you say that my comment is reductive. It's adding nuance to the topic at hand, rather than removing it. The original comment talks about a situation where we constrain ourselves to "rigid types"; t
40.
by arxanas 3y ago
For the case of resource usage, you can see work like https://link.springer.com/chapter/10.1007/978-3-030-81685-8_... "Synthesis with Asymptotic Resource Bounds" which implements bounded resource checkin
41.
by arxanas 3y ago
Rice's theorem states that there is no general procedure to determine if an arbitrary Turing machine has some property. We are restricting ourselves to programs which typecheck under a certain type system, so there will certainly be
42.
Encoding ML-style modules in Rust(blog.waleedkhan.name)
2 points by arxanas 3y ago|0 comments
43.
by arxanas 3y ago
Why would you need substructural typing to emulate Typescript? Is there a substructural type system feature in TS? You can accomplish width subtyping with OCaml's "polymorphic variants", which could be used to emulate TS unio
44.
Quickly Formatting a Stack of Commits(blog.waleedkhan.name)
2 points by arxanas 4y ago|0 comments
45.
Improving incremental test times in Rust(blog.waleedkhan.name)
1 points by arxanas 4y ago|0 comments
46.
Interactive Blogs(blog.waleedkhan.name)
3 points by arxanas 4y ago|0 comments
47.
by arxanas 4y ago
I right-clicked commits not reachable from `HEAD` and the Edit Commit Message option was disabled, so I'm assuming it can only reword commits reachable from `HEAD`.
48.
by arxanas 4y ago
Yes, it's entirely client-side.
49.
by arxanas 4y ago
Yes, I am the author. > I hope my comments did not come across as too negative. Not at all! > guess it's time to setup rust and check this out It's also available on many package managers, such as Homebrew and Nix, although
50.
by arxanas 4y ago
Sorry, my wording was imprecise, see my comment here https://news.ycombinator.com/item?id=34301971
51.
by arxanas 4y ago
> This seems to be about working with commits, including branched trees/graphs, without creating a named branch..? That's correct.
52.
by arxanas 4y ago
https://github.com/martinvonz/jj and http://sapling-scm.com/ are good steps in this direction!
53.
by arxanas 4y ago
> Is this for a case where a bunch of people branch from master@HEAD (lets call this A), then you need to modify A, so you then need to rebase each branch that branched from A individually? Mainly it's for when you branch from A m
54.
by arxanas 4y ago
Trunk-based development is still in use at large companies. Usually they use something like Gerrit or Phabricator. You could try tools like https://graphite.dev/ or https://reviewable.io/ , or Meta's Sa
55.
by arxanas 4y ago
Thanks. I confirmed that you can reword a commit which is reachable from `HEAD`, but not those on other branches in this way, similar to Sublime Merge elsewhere in the comments.
56.
by arxanas 4y ago
It is not! See https://github.com/arxanas/git-branchless/wiki/Architecture#...
57.
by arxanas 4y ago
It's true that it's easy to forget one's early challenges, but we have empirical support that design decisions such as the staging area are objectively difficult for beginners to adopt. See https://investigating-ar
58.
by arxanas 4y ago
Apologies, but I misunderstood what you meant by the "downstream" conflict situation. That's not possible in git-branchless, but it is possible in Jujutsu, since it stores conflicts as first-class objects, so it can actually
59.
by arxanas 4y ago
On the contrary: I myself have implemented these better operations, and they work great. They also exist in some other VCSes, such as Mercurial and Jujutsu. You can see the `git-branchless` column in the table for comparison with the other
60.
by arxanas 4y ago
For example, Git is somewhat ambivalent on the topic, but Fossil SCM is notably very much against rebasing/rewriting history.

More ›