We will be having new functions in TAPE called EncodeAny and DecodeAny (subject to change) which will be able to take in an any value and encode it to an encoder or decode it from a decoder. Structs should be supported (when a KTV value is encountered) as long as they have struct tags. Such a struct would look something like this:
The tag's value would correspond to the field's table key, and it would be hexadecimal ranging 0000-FFFF, and exactly 4 digits to emphasize that it is not a decimal number.
We will be having new functions in TAPE called EncodeAny and DecodeAny (subject to change) which will be able to take in an `any` value and encode it to an encoder or decode it from a decoder. Structs should be supported (when a KTV value is encountered) as long as they have struct tags. Such a struct would look something like this:
```go
type Thing struct {
SomeField string `tape:"0000"`
OtherField string `tape:"0001"`
AnotherField string `tape:"0002"`
}
```
The tag's value would correspond to the field's table key, and it would be hexadecimal ranging 0000-FFFF, and exactly 4 digits to emphasize that it is not a decimal number.
With a link to the HOPP repository. Maybe we should change the module name before, though.
When this change is implemented, merged, and released, we must add `tape` to this list: https://go.dev/wiki/Well-known-struct-tags
With a link to the HOPP repository. Maybe we should change the module name before, though.
sashakoshka
added a new dependency 2025-06-27 11:36:12 -06:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
We will be having new functions in TAPE called EncodeAny and DecodeAny (subject to change) which will be able to take in an
anyvalue and encode it to an encoder or decode it from a decoder. Structs should be supported (when a KTV value is encountered) as long as they have struct tags. Such a struct would look something like this:The tag's value would correspond to the field's table key, and it would be hexadecimal ranging 0000-FFFF, and exactly 4 digits to emphasize that it is not a decimal number.
When this change is implemented, merged, and released, we must add
tapeto this list: https://go.dev/wiki/Well-known-struct-tagsWith a link to the HOPP repository. Maybe we should change the module name before, though.