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.
This PR was created automatically. Merging it will create a new release for 0.10.0
Breaking Changes
Consensus diffs
#270 by @lukechampine
This replaces the
ForEach
update API with slices of "diffs" -- new types wrapping the various element types. This was originally intended as an ergonomics improvement (since it's annoying to e.g. break out of aForEach
callback), but it ended up significantly simplifying mostMidState
-related code: it consolidated the interrelated maps withinMidState
, and enabled a much saner rewrite of the update JSON types.I originally left the
ForEach
methods in place (with a// Deprecated
warning), but later removed them entirely; we're going to update all the callsites incoreutils
anyway, so there's little reason to keep them around. (ForEachTreeNode
remains, though, since it's used byexplored
.)Fixed a panic when unmarshalling unknown spend policy types
An error will now be returned when trying to encode a transaction with an unset
SpendPolicy