[#104169] [Ruby master Feature#17938] Keyword alternative for boolean positional arguments — matheusrichardt@...

Issue #17938 has been reported by matheusrich (Matheus Richard).

12 messages 2021/06/04

[#104213] [Ruby master Feature#17942] Add a `initialize(public @a, private @b)` shortcut syntax for defining public/private accessors for instance vars — tyler@...

Issue #17942 has been reported by TylerRick (Tyler Rick).

6 messages 2021/06/09

[#104288] [Ruby master Bug#17992] Upstreaming the htmlentities gem into CGI#.(un)escape_html — alexandermomchilov@...

Issue #17992 has been reported by AMomchilov (Alexander Momchilov).

9 messages 2021/06/15

[#104338] [Ruby master Misc#17997] DevelopersMeeting20210715Japan — mame@...

Issue #17997 has been reported by mame (Yusuke Endoh).

10 messages 2021/06/17

[#104361] [Ruby master Bug#18000] have_library doesn't work when ruby is compiled with --disable-shared --disable-install-static-library — jean.boussier@...

Issue #18000 has been reported by byroot (Jean Boussier).

9 messages 2021/06/18

[#104401] [Ruby master Feature#18007] Help developers of C extensions meet requirements in "doc/extension.rdoc" — mike.dalessio@...

Issue #18007 has been reported by mdalessio (Mike Dalessio).

16 messages 2021/06/25

[#104430] [Ruby master Bug#18011] `Method#parameters` is incorrect for forwarded arguments — josh.cheek@...

Issue #18011 has been reported by josh.cheek (Josh Cheek).

12 messages 2021/06/29

[ruby-core:104314] Re: Float truncate

From: Austin Ziegler <halostatue@...>
Date: 2021-06-16 17:32:23 UTC
List: ruby-core #104314
This isn窶冲 related to float truncation, it窶冱 related to the
approximate nature of float.

[4] pry(main)> 291.4 * 100
=> 29139.999999999996

https://bugs.ruby-lang.org/#Floating-point-numbers

If your client needs accuracy on this, they should be using BigDecimal.

[12] pry(main)> BigDecimal('291.4').truncate(2)
=> 0.2914e3

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?

-a

On Wed, Jun 16, 2021 at 8:25 AM Eustテ。quio Rangel
<eustaquiorangel@gmail.com> wrote:
>
> Hi!
>
> A customer just noticed a weird behaviour on its app, regarding float truncate. I know floats are wild beasts and we can have some surprises as stated on the truncate docs as
>
> (0.3 / 0.1).truncate
> => 2
>
> But let me show what they found:
>
> > 291.1.truncate(2)
>  => 291.1
> > 291.2.truncate(2)
>  => 291.2
> > 291.3.truncate(2)
>  => 291.3
> > 291.4.truncate(2)
>  => 291.39 <------------------ here!
> > 291.5.truncate(2)
>  => 291.5
>
> Notice 291.4 truncating to 2, returns 291.39! They have another number like .3 that truncates to .2, so I just took a look on rb_float_floor and found that 291.4 is converted to 29139.000000 after powered and sent to
>
> floor(number * f)
>
> and then proceeds to DBL2NUM when it returns 291.39. I advised them to use another approach other than truncate (round don't work for them because of the ceil/floor operation) but I'm curious if it is a known behaviour of float truncate.
>
> Thanks.
>
>
> Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>



-- 
Austin Ziegler 窶「 halostatue@gmail.com 窶「 austin@halostatue.ca
http://www.halostatue.ca/ 窶「 http://twitter.com/halostatue

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread