Refactor STB/STL again to have versioned filers instead of policy#1226
Merged
Refactor STB/STL again to have versioned filers instead of policy#1226
Conversation
The fallback/retry code executed by the int[32]PtrAtOffset:put: methods of External.Address are not consistent with those of ByteArray.
Serialize and deserialize capabilities should be independent. STL for view resources is now generally stable. This means views can be resaved and the source code should only change if the view has been edited or contains class that have changed format. It should also help to see just the actual changes that have occurred, although this still isn't easy in what is essentially a serialized object format.
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
1 participant
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.
Serialize and deserialize capabilities should be independent.
STL for view resources is now generally stable in the sense that the resource method source should not change unless the view is actually changed. This means views can be resaved and the source code should only change if the view has been edited or contains class that have changed format. It should also help to see just the actual changes that have occurred, although this still isn't easy in what is essentially a serialized object format.