Hi devs,

I noticed the other day that the BigInteger converter is doing its own parsing 
of hexadecimal strings at 
  I'm pretty sure it's not working for most large number cases, including a few 
in the docs for that class like 0xFFFFAC. Before I open another jira ticket 
though, can you tell me why we're reimplementing hex string parsing instead of 
using BigInteger("somehexstring", 16)? It's cool if that's an oversight but I 
want to make sure I'm not missing some subtle use case.


Sent from a tiny keyboard

Reply via email to