and_v() must never be ’d’. This is not a bug fix since this was unreachable in valid Miniscripts: the first sub of an and_v() must be of type V, which conflicts with (i.e. never has) property ’d'.
and_v() must never be ’d’. This is not a bug fix since this was unreachable in valid Miniscripts: the first sub of an and_v() must be of type V, which conflicts with (i.e. never has) property ’d'.
and_v() must never be 'd'. This is not a bug fix since this was
unreachable in valid Miniscripts: the first sub of an and_v() must be of
type V, which conflicts with (i.e. never has) property 'd'.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
See the guideline for information on the review process.
If your review is incorrectly listed, please copy-paste <!–meta-tag:bot-skip–> into the comment that the bot should ignore.
Code Review ACK 4fab35cf88c048d2784fe6d71d3f83cc4e420879. The specification says and_v never has the "d" property, while the code seems to give it the "d" property if both sub-fragments have "d" as well. This has no observable effect, because any valid miniscript won’t have "d" in the left sub-fragment.
Let’s still wait for CI and run some extra fuzzing cycles…
darosior
DrahtBot
sipa
achow101
Labels
Descriptors