test(cbor): number precision error in decoding test

[BlackAsLight]

Fixes: https://github.com/denoland/std/actions/runs/11310597614/job/31455830417#step:4:1

Due to the way JavaScript numbers work, numbers past 2 ** 53 lose precision. Weirdly though sometimes when converting them to BigInts they may gain more precision than they originally had.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.57%. Comparing base (3927872) to head (6960e91).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6115   +/-   ##
=======================================
  Coverage   96.56%   96.57%           
=======================================
  Files         534      534           
  Lines       40550    40550           
  Branches     6085     6085           
=======================================
+ Hits        39159    39163    +4     
+ Misses       1347     1343    -4     
  Partials       44       44           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kt3k]

LGTM. Thanks!

[kt3k]

BTW is it a good idea to show warnings or something when the input of encodeCbor is a number > Number.MAX_SAFE_INTEGER?

[BlackAsLight]

BTW is it a good idea to show warnings or something when the input of encodeCbor is a number > Number.MAX_SAFE_INTEGER?

I don't think that's necessary as anyone who is working with numbers that big should be aware of how JavaScript reacts with it.

[kt3k]

Fair enough