Yes. I thought the same. It’s very focused on what the trust-dns libraries need at the moment, and I want to see if over time we can get rid of some of the unverified
uses. Maybe at that point?
As to the name Restrict
is the name of the type, and RestrictedMath
for the trait and math functions. Is this the best name? I’m sure not. You have some good other options. I didn’t use Untrusted
because I didn’t want confusion with the untrusted library, which I plan to make more extensive use of. Unverified
is definitely an option Verified
is currently the type name of the return from verify
. We could change it to that, but I wanted a name that really got the idea across that you should be wary of the data contained in the type.
So in that sense Restrict
Is more about the fact that the data is actively being restricted in its usage. That is, it’s safe usage is limited.