-
Notifications
You must be signed in to change notification settings - Fork 171
cue: support type conversions #3
Comments
Want to calculate Sha1 checksum and then encode it into Base64 string, but I'm unable to do that, because:
|
And in that case, the main root that |
It still makes sense to support conversions, but it probably makes sense to interpret This would be a relatively minor, but breaking change, but presumably a welcome one and I think it is worth it. Feedback welcome. |
@mpvl I wondering if there is a working example of And it's a definitely different issue than conversion between types. |
I think it is unlikely. We are still in a change where changes can be made if it makes sense (with due consideration of course), but here I think it is obvious. These APIs were generated before CUE had a bytes type. Now it does, it seems consistent to use it not only for []byte, but also [...]byte. |
I've checked, and such a change in interpretation would only affect the crypto packages. |
This issue has been migrated to cue-lang/cue#3. For more details about CUE's migration to a new home, please see cue-lang/cue#1078. |
This is a tracking issue for the implementation of the commented out sections in the spec for conversions.
For instance:
But also to convert a struct to a specific struct type. The latter is quite handy for various purposes.
The text was updated successfully, but these errors were encountered: