Conversation
…:builder::Error` Co-authored-by: Jack Grigg <jack@electriccoin.co>
1e2b652 to
aa9015d
Compare
Co-authored-by: Jack Grigg <jack@electriccoin.co> Co-authored-by: Kris Nuttycombe <kris@nutty.land>
aa9015d to
4fbdd64
Compare
There was a problem hiding this comment.
Ah, no more transaction::components::orchard::builder mod, with all that MaybeOrchard stuff... It means that a builder now has the orchard-related methods even if it's not provided with an orchard anchor, which is now a runtime error when you try to call them with no anchor...but on the other hand, it's makes the implementation so much cleaner.
It's a tradeoff, but one that I'm fine with! The other change I've noticed is assert_matches, which just makes more sense than Eqable errors
Not only that, there was already a runtime error that had to be raised if NU5 wasn't active, and so statically making those methods unavailable strictly increased the space of types that implementations had to deal with without reducing the number of possible runtime errors at all. So overall, the |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #863 +/- ##
==========================================
- Coverage 69.97% 69.76% -0.22%
==========================================
Files 124 124
Lines 11551 11618 +67
==========================================
+ Hits 8083 8105 +22
- Misses 3468 3513 +45
☔ View full report in Codecov by Sentry. |
…ror::OrchardAnchorNotAvailable` Co-authored-by: str4d <thestr4d@gmail.com>
Co-authored-by: str4d <thestr4d@gmail.com>
Subsumes #583