Age | Commit message (Collapse) | Author |
|
https://github.com/ruby/bigdecimal/commit/7504871c48
|
|
https://github.com/ruby/bigdecimal/commit/5c808eeabb
|
|
[ci-skip]
https://github.com/ruby/bigdecimal/commit/905d0345ec
|
|
https://github.com/ruby/bigdecimal/commit/741fb3e00f
|
|
|
|
https://github.com/ruby/bigdecimal/commit/e68f1eb33a
|
|
https://github.com/ruby/bigdecimal/commit/981dc48f95
https://github.com/ruby/bigdecimal/commit/9ecf880ec04
|
|
https://github.com/ruby/bigdecimal/commit/7e80e6e145
https://github.com/ruby/bigdecimal/commit/0ed7846e8c
|
|
https://github.com/ruby/bigdecimal/commit/458eb66c49
|
|
https://github.com/ruby/bigdecimal/commit/93fc392640
https://github.com/ruby/bigdecimal/commit/a90d13c4d0
|
|
https://github.com/ruby/bigdecimal/commit/12296dcb90
|
|
Fix https://github.com/ruby/bigdecimal/issues/70
[Bug #13331]
https://github.com/ruby/bigdecimal/commit/aa536cd4b5
|
|
|
|
* remove duplicated include
* Make BigDecimal#round with argument < 1 return Integer
Fixes [Bug #12780]
* Use a higher default precision for BigDecimal#power and #**
When a fractional power is given, increase the precision if the
precision isn't specified via power's second argument:
Float: increase by 15 (rough number of decimal precision in float)
BigDecimal: increase by adding similar precision modifier as done to
calculate the base precision.
Rational: double the precision, since a BigDecimal is created, but
the created BigDecimal uses the same precision.
Increasing the precision for these power calculations has the obvious
tradeoff of making the calculations slower.
Fixes Ruby Bug #17264
* Use DBLE_FIG for a Float value
* Version 2.0.1
Co-authored-by: pavel <pavel.rosicky@easy.cz>
Co-authored-by: Jeremy Evans <code@jeremyevans.net>
Notes:
Merged-By: mrkn <mrkn@ruby-lang.org>
|
|
alway -> always
Notes:
Merged: https://github.com/ruby/ruby/pull/3646
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3347
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3346
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3338
|
|
|
|
https://github.com/ruby/bigdecimal/commit/3fa4f2ac67
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
Fixes #159
https://github.com/ruby/bigdecimal/commit/57ee92e700
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
https://github.com/ruby/bigdecimal/commit/79a819d205
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
https://github.com/ruby/bigdecimal/commit/61ec452599
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
https://github.com/ruby/bigdecimal/commit/97e794ac97
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
This leaves the default definition, which will raise FrozenError.
https://github.com/ruby/bigdecimal/commit/05e843d838
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
https://github.com/ruby/bigdecimal/commit/00795cb01f
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
Both BigDecimal#clone and BigDecimal#dup return self, there is no
reason to have initialize_copy exposed as a Ruby method.
The same is true for initialize_clone and initialize_dup.
https://github.com/ruby/bigdecimal/commit/aaf237fa9e
Notes:
Merged: https://github.com/ruby/ruby/pull/3295
|
|
dd0c75fdc2104a6ba38b68d4431a572504a3bbc2
|
|
`#define NDEBUG` produces "macro redefined" warnings when it is already
defined via cppflags
|
|
To fix build failures.
Notes:
Merged: https://github.com/ruby/ruby/pull/3079
|
|
This shall fix compile errors.
Notes:
Merged: https://github.com/ruby/ruby/pull/3079
|
|
|
|
Split ruby.h
Notes:
Merged-By: shyouhei <shyouhei@ruby-lang.org>
|
|
https://github.com/advisories/GHSA-jppv-gw3r-w3q8
|
|
Notes:
Merged-By: mrkn <mrkn@ruby-lang.org>
|
|
This removes the taint checking. Taint support is deprecated in
Ruby 2.7 and has no effect. I don't think removing the taint
checks in earlier ruby versions will cause any problems.
https://github.com/ruby/bigdecimal/commit/1918d466f3
|
|
Sync to ruby/bigdecimal@92356ba71c6bd325b0ab618c634a7aecf8cdc767
Notes:
Merged-By: mrkn <mrkn@ruby-lang.org>
|
|
This is how Kernel#{Array,String,Float,Integer,Hash,Rational} work.
BigDecimal and Complex instances are always frozen, so this should
not cause backwards compatibility issues for those. Pathname
instances are not frozen, so potentially this could cause backwards
compatibility issues by not returning a new object.
Based on a patch from Joshua Ballanco, some minor changes by me.
Fixes [Bug #7522]
Notes:
Merged: https://github.com/ruby/ruby/pull/2473
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* https://github.com/ruby/bigdecimal/compare/v1.4.1..v1.4.2
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66574 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
* https://github.com/ruby/bigdecimal/compare/v1.4.0..v1.4.1
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66535 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
* https://github.com/ruby/bigdecimal/compare/v1.4.0.pre.20181220a..v1.4.0
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66516 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
* https://github.com/ruby/bigdecimal/compare/v1.4.0.pre.20181214a..v1.4.0.pre.20181220a
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66473 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|
|
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@66397 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
|