Controversial opinion: what a waste of attention. We should have a declared range of versions (we attest) our libraries support, and separately a freeze file for reproducible test running (and other code executions, like runMain, console, what have you).https://twitter.com/fst9000/status/1227149976196845569 …
-
-
I've been thinking a lot about our chat about this since we spoke in December, and I've more or less come round to your approach.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The problem is one that fundamentally boils down to making changes to a persistent Merkle DAG where cross-vertex changes are non-atomic. We can either make the DAG non-persistent, or we can accept that there will be quite a few independent changes.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Every solution to this problem boils down to one of those two. A non-persistent DAG, by definition, violates reproducibility in some form (note that freeze files simply choose a middle ground between the two extremes). A persistent DAG will be noisy without atomic updates.
-
I think there's a good compromise though: We can have builds which are immutable and repeatable, but where nonbreaking changes can be introduced trivially with the user's intervention, and larger changes less trivially (but, as necessary). (Full explanation won't fit in a tweet.)
- Show replies
New conversation -
-
-
Atomic updates, by definition, cannot be guaranteed because we aren't just dealing with one DAG, but technically an open set of partially-overlapping DAGs. That's a particularly complex issue, and due to the openness of the set, we cannot guarantee global control over all of it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Ultimately, I think that the final evolution of Scala Steward is probably pretty close to something that
@dcsobral is working on right now, which employs a stronger semantic understanding of specific subgraphs to eliminate multi-path propagation noise.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.