From: 0x0dea+redmine@...
Date: 2015-07-10T15:39:10+00:00
Subject: [ruby-core:69941] [Ruby trunk - Feature #10594] Numeric#clamp

Issue #10594 has been updated by D.E. Akers.


Ferdinand Niedermann wrote:
> That doesn't really change anything

You're right, of course. I'm not sure why I read it as "raise unless `max > min`". The error message is still slightly ill-worded, but everything else looks good. I hope `#clamp` makes it in. The `sort[1]` trick is nice, but it's a little too "clever".

----------------------------------------
Feature #10594: Numeric#clamp
https://bugs.ruby-lang.org/issues/10594#change-53368

* Author: Chris Johnson
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
This is basically a re-opening of the feature request of issue#4573 (https://bugs.ruby-lang.org/issues/4574), which was closed due a naming debate.

It seems the standard naming for restricting a number to a specified range is indeed 'clamp'.  (1)(2)(3)

As such, can we use Yusuke Endoh's original patch with the naming adjustments?  If so, I can provide accordingly.

Cheers.

(1) http://www.rubydoc.info/github/epitron/epitools/Numeric:clamp
(2) http://stackoverflow.com/questions/12020787/is-there-a-limit-clamp-function-in-ruby
(3) https://developer.gnome.org/glib/stable/glib-Standard-Macros.html#CLAMP:CAPS


---Files--------------------------------
num_clamp.c (427 Bytes)


-- 
https://bugs.ruby-lang.org/