There are a lot of in-flight PRs (#253, #254, #209, etc.) that change the public API of the library. Rather than incrementally updating the Changlelog (and then backing out some of those entries in the next PR in the line), do this comprehensively once master is caught up with the branch used by librustzcash.
There are a lot of in-flight PRs (#253, #254, #209, etc.) that change the public API of the library. Rather than incrementally updating the Changlelog (and then backing out some of those entries in the next PR in the line), do this comprehensively once master is caught up with the branch used by librustzcash.