Other than decreased performance and not using literals and operators directly, are there any other disadvantages to using BigInt and BigDecimal (in particular in Java)?
The arbitrary precision may cause your bignums to balloon out of control in memory/cpu usage after repeated multiplication, unless you can prove that it will not. For example:
double x = 1;
while (true){
x *= Math.exp((Math.random()*2 - 1) / 1000);
}
Would work perfectly fine with floats and x will remain about 1, but with BigDecimal it will grind to a halt.
I think you pretty well summed it up. Decreased performance and more difficult to code and maintain (significantly so in comparison to native values and simple operators). Don’t get me wrong these classes absolutely have their place, but I wouldn’t use them without a compelling reason.
They do the job but they are clunkier to use and use significantly more memory and processing power than the primitive data types. Use them if you need them, but don’t use them when a primitive would do the job just as well.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
The arbitrary precision may cause your bignums to balloon out of control in memory/cpu usage after repeated multiplication, unless you can prove that it will not. For example:
Would work perfectly fine with floats and x will remain about 1, but with BigDecimal it will grind to a halt.
Interesting. Is there a way to set a limit to the size of individual instances?
Give it a MathContext with the max precision that you want to allow.
Thanks, that doesn’t sound so bad.
I think you pretty well summed it up. Decreased performance and more difficult to code and maintain (significantly so in comparison to native values and simple operators). Don’t get me wrong these classes absolutely have their place, but I wouldn’t use them without a compelling reason.
Serialisation, marshalling issues and mental overhead of using compareTo
They do the job but they are clunkier to use and use significantly more memory and processing power than the primitive data types. Use them if you need them, but don’t use them when a primitive would do the job just as well.