On compound interests, as I already said earlier, I would normally use the standard exponential formulas and, of course, end up with floats. For example, with a 1.6% interest rate over 10 years compound annually and an initial value of 10,000: 
> my $start_val = 10_000;
10000
> my $end_val = $start_val * (1 + 0.016)**10
11720.2555035677
> say $end_val.WHAT
(Num)

[download]
But if I make the same calculation without the exponential formula within a a loop: 
> my $end_val = $start_val;
10000
> $end_val *= 1.016 for 1..10
Nil
> say $end_val
11720.25550356773576542599
> say $end_val.WHAT
(Rat)
> say $end_val.nude
(17464541649174296506384 1490116119384765625)

[download]
As you can see, I still get a Rat. And, BTW, I get a better accuracy with this loop, but, in fact, we don't really care about this better accuracy, since the final monetary amount will be rounded to two decimal places anyway (although you could conceivably find start values for the error on the floating point value would propagate and make a 1 cent difference on the final rounded value). To tell the truth, I was fairly lucky here: with just 11 years, I would no longer get a Rat.

And, of course, the loop will fall back to floats if we compound the interests monthly: 

> my $end_val = $start_val * (1 + 0.016/12)**120
11733.8581431786
> say $end_val.WHAT
(Num)
>
> my $end_val = $start_val;
10000
> $end_val *= 1 + 0.016/12 for 1..120
Nil
> say $end_val
11733.8581431787
> say $end_val.WHAT
(Num)

[download]
We get the same result (there is a rounding difference of 1 on the last digit, but we don't care, it will be rounded to 11,733.86 anyway).

So yes, we often fall back on floats when compounding interests, but that really doesn't matter, nobody cares.

A company for which I worked as a freelance consultant had to spend tens of thousands of euros in a software project to fix invoices which looked wrong because of rounding problems on FP arithmetic inaccuracies. One invoice in tens of thousands looked wrong (the total was actually accurate, but the individual values and subtotals did not seem to match); some consumers complained and the legal and/or tax authorities demanded a correction. All these amounts would have matched properly if the calculations had been done with Perl 6 Rat type.

In reply to Re^9: Reasons for Using Perl 6 by Laurent_R
in thread Reasons for Using Perl 6 by aartist

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.