Better discriminant types, transmute special cases, onInt attributes
#778
+68
−12
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.
rvalueDiscriminantoperation was unconditionally returning 128-bit integers, which turns out to be wrong. We now consult the layout to return the correct bit width (but still always unsigned as this seems to be an invariant).Closes Inconsistent
uinttypes in proofsinitialize_account*solana-token#41transmuteare implemented, removingthunks thattransmutewould have created before.transmutes through a given type back to the original type are eliminatedtransmutefrom anIntegerto anenumwithout fields followed by adiscriminantoperation, the original integer value is returned as the discriminant.onIntfunction was missingpreserves-definednessattributes on its equation so booster did not apply it