[ruby-core:104467] Re: Float truncate

I believe this to be a bug; I opened https://bugs.ruby-lang.org/issues/1801=
8

Thanks for reporting this


On Wed, Jun 16, 2021 at 3:36 PM Eust=C3=A1quio Rangel <eustaquiorangel@gmai=
l.com>
wrote:

> Hey Austin!
>
> Em qua., 16 de jun. de 2021 =C3=A0s 14:32, Austin Ziegler <halostatue@gma=
il.com>
> escreveu:
>
>> This isn=E2=80=99t related to float truncation, it=E2=80=99s related to =
the
>> approximate nature of float.
>>
>> [4] pry(main)> 291.4 * 100
>> =3D> 29139.999999999996
>>
>> https://bugs.ruby-lang.org/#Floating-point-numbers
>
>
> Yeah, meanwhile I was taking a look on some of the concepts, thanks for
> pointing out this URL! As I said, floats are known to be wild math beasts=
.
> :-)
>
>> If your client needs accuracy on this, they should be using BigDecimal.
>>
>> [12] pry(main)> BigDecimal('291.4').truncate(2)
>> =3D> 0.2914e3
>>
>
> Thanks! We also made some monkey patching on Float, to allow they truncat=
e
> converting first on a String.
>
> As a side note to the maintainers of the RubyMine gateway, this email
>> did not open a ticket in RubyMine. Is the gateway broken again?
>>
>
> I also noticed that.
>
> Thanks!
>
> Unsubscribe: <mailto:[e-mail]?subject=3Dunsubscrib=
e>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
>

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>