Faye Amacker

@SupunS > On a side note, I noticed that when the resource array is loaded from storage, all elements seem to be also 'loaded' every time (so they get iterated...

Hi, I stumbled across this thread while adding TinyGo support to fxamacker/cbor. I created branch [fxamacker/cbor-tinygo](https://github.com/fxamacker/cbor/tree/fxamacker/cbor-tinygo) this weekend based on fxamacker/cbor [v2.5.0-beta4](https://github.com/fxamacker/cbor/releases/tag/v2.5.0-beta4). It passes codec tests when compiled with TinyGo...

Hi @Exaelitus > To be specific, I mean simple vectors like "abc". "cba", "cab", "HelloWorld" etc. Rather than the 16k subroutine for data which I would then also have to...

> That errored out because fxamacker/cbor returns the avatar and banner maps as map[interface{}][interface{}]. Those maps have only string keys, but a generic cbor parser can't assume that. Hi @jmhodges,...

@SaveTheRbtz Thanks for opening this issue and also PR #268. > Suggested Solution > In the ideal world, each slab storage instance can have a goroutine pool of encoders ready...

@espoal > I would like to add that it would be nice to have End Of Sequence error. It would be different from io.EOF because it would cover the case...

Support for bfloat16 is also requested in comments at #46

> Currently, when cbor.Unmarshal is called with a byte string data item and time.Time as destination type, it causes UnmarshalTypeError with message "cbor: cannot unmarshal byte string into Go value...

@benluddy Thanks for providing context and use case. > On second look, I see that the implementation of parseToTime is essentially "decode into interface{}, then type assert to map back...

> Waiting for https://github.com/fxamacker/cbor/pull/503 to merge as this option should be implemented on top of that change. Thanks for letting me know! I reviewed the PR tonight: - #503