[tannevaled]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/go-dataframe/dataframe	v0.1.0 → v0.2.0
github.com/go-embedded-ruby/ruby	v0.8.0 → v0.8.1
github.com/go-ndarray/ndarray	v0.12.0 → v0.18.0
github.com/go-numerics/special	v0.1.0 → v0.2.0

---

Release Notes

go-dataframe/dataframe (github.com/go-dataframe/dataframe)

v0.2.0

Compare Source

go-embedded-ruby/ruby (github.com/go-embedded-ruby/ruby)

v0.8.1: — a missing argument is MRI's error, not a Go panic

Compare Source

One commit since v0.8.0: the arity fix (#​824), closing #​820.

A missing argument is MRI's error again, not a Go panic

31 methods across FFT and Image read their arguments by index without checking how many they had been given. A call with too few arguments indexed past the end of the slice, and the Go panic was recovered and re-raised as an ArgumentError — the right class, by accident, with a message that came from Go's runtime rather than from Ruby.

FFT.fft                 # before: a recovered index-out-of-range
                        # now:    ArgumentError, MRI's wording and arity

The fix puts the arity at the registration site, so it cannot be forgotten when a method is added:

def("fft", 1, 1, func(...) {...})
def("fftfreq", 1, 2, ...)       // n, and an optional sample spacing
def("spectrogram", 4, 5, ...)

Ranges are real optional arguments, not slack: Image#set is 5, 6.

Two tests, because Image is not in every build

Image is excluded from the rbgo_core build and FFT is not, so a single test naming both went red on the core lane. They are split by build tag, and each counts what it walked — 3 and 34, 17 methods — so a census that silently stopped finding methods would fail rather than pass quietly. Verified under both tags: 23 tests on the default build, 6 on rbgo_core, no "no tests to run".

Known, and already in flight

The README's BigDecimal entry lists sqrt, which is not bound — BigDecimal("2.0").sqrt(0) raises NoMethodError. That is older than this release and is corrected in #​826; the method itself is #​825, and the gap is upstream, in go-ruby-bigdecimal/bigdecimal, which has no square root at all.

Measured on 664fcfe with all 10 lanes green.

go-ndarray/ndarray (github.com/go-ndarray/ndarray)

v0.18.0

Compare Source

v0.17.0

Compare Source

v0.16.0

Compare Source

v0.15.0

Compare Source

v0.14.0

Compare Source

v0.13.0

Compare Source

go-numerics/special (github.com/go-numerics/special)

v0.2.0

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[tannevaled]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 1 additional dependency was updated

Details:

Package	Change
github.com/go-fft/fft	v0.23.0 -> v0.27.1