Report type when erroring on unsupported-type

[Kristjansson]

When logging the value, it's not always clear the exact type that's causing failure (ArrayList vs vec for example). Adding the type makes this error message a little more informative.

[codecov-io]

Codecov Report

Merging #15 into master will decrease coverage by 1.8%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
- Coverage     100%   98.19%   -1.81%     
==========================================
  Files          13       13              
  Lines         811      831      +20     
  Branches        0        4       +4     
==========================================
+ Hits          811      816       +5     
- Misses          0       11      +11     
- Partials        0        4       +4

Impacted Files	Coverage Δ
src/clj_cbor/codec.clj	100% <100%> (ø)	⬆️
src/clj_cbor/data/simple.clj	28.57% <0%> (-71.43%)	⬇️
src/clj_cbor/data/tagged.clj	50% <0%> (-50%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 875784b...b1af7fc. Read the comment docs.

[greglook]

Seems like a useful addition to the error case - could you also cover this with a test?

[greglook]

Two thoughts here - first, class is generally more appropriate than type, since the latter will return you (:type (meta x)) which is (obviously) user-modifiable. Given that the default dispatch function is class this would also match the behavior better.

Second thought builds on the first one, which is that this case occurs when write-handled falls through because there's no handler for the dispatched type. It may be more useful to make this data include the dispatch function's return value, since that's what's actually used for the handler behavior.

[greglook]

Going to merge this so you have a commit, will make the change I suggested directly.