Closed
Conversation
Member
Author
|
As I discussed with @cart on Discord, my explanation of data access compatibility doesn't match the current implementation. However, I believe they're formally equivalent, and the current explanation nicely unifies the incompatibility checks done by system parameters and ambiguities (what I'm calling hypothetical incompatibility) with the checks done by the scheduler (factual incompatibility). This framing is also, IME, very useful for reasoning about parallelizability of complex data access patterns. DIscussion link for the equivalency: bevyengine/bevy#3119 |
Member
|
Closing as we will very likely start new PRs (and use this as a reference) when we pick up the new book effort again. |
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
2 participants
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.
If you'd like to read (or review) this PR, you'll need to:
With #182 in a reasonable state, it's time to dive into the next chapter! I'm opening this early, so others can watch, learn and provide feedback as I work.
Contents: