Open
Conversation
… two sync protocols
…nct points between spawning and starting a thread
…around a bit on spawn to ensure the correct context and not a copy is initialised
…que, and use refs instead of shared ptrs
… resolution in branching
…ol directories and abstracting it out of the general thread state
…, lazy is unfinished
…are failing as a result of no read of the conflict variables
…and interactive graphing too
…and interactive graphing too
… detecting conflicts that came before suppressing writes, and updating command line opts and testsuite
…red on failing, adding infrastructure to let prptocols decide what is a scheduling point
…owing a bug, more scheduling points on spawn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refactor a bunch of logic to enable two strategies for gitmem, linear and branching