You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MAXIMUM-OF and MINIMUM-OF don't actually return the maximum or minimum of a series, they return the series at the position of the maximum or minimum. Gregg has suggested that these be renamed to FIND-MAX and FIND-MIN instead. This would allow us to create different MAXIMUM-OF and MINIMUM-OF functions which actually do return the maximum and minimum values (see #1972 for such a proposal).
Normally this would be against the (defacto) legacy naming rules, but we make an exception for functions that are rarely used and really badly named, especially when we have a much better use for the name. MAXIMUM-OF and MINIMUM-OF fit that description.
This issue was last mentioned in #1818, but was first brought up in AltME years ago. See also #428 for issues that relate to /skip behavior of these functions.
Ch.Ensel (aka ChristianE) suggested that these be named AT-MAXIMUM and AT-MINIMUM instead in #1818. However, the functions don't really seem related to AT. For AT, you already know and specify the position; for these functions, you are trying to find the position. These really seem like they're more related to FIND.
Rebolbot commented on Mar 13, 2013:
Submitted by:Gregg
I agree with this change. From the old AltMe chat on it, Ladislav was against it, but suggested doc string changes would help. Here were my proposals at that time:
FIND: "Returns the series where the value is found, or none if the value is not found."
FIND-MAX: "Returns the series where the largest value is found, or none if the series is empty."
AT-MAX: "Returns the series at the position where largest value is found, or none if the series is empty."
AT-MAX: "Returns the series at the largest value, or none if the series is empty."
I still prefer the FIND* variant over AT*, but either is better than what we have now.
Rebolbot commented on Feb 20, 2014:
Submitted by:BrianH
Requested Oldes/Rebol-wishes#58 to be better able to implement functions like these with the #428 record comparison rules.
Submitted by: BrianH
MAXIMUM-OF and MINIMUM-OF don't actually return the maximum or minimum of a series, they return the series at the position of the maximum or minimum. Gregg has suggested that these be renamed to FIND-MAX and FIND-MIN instead. This would allow us to create different MAXIMUM-OF and MINIMUM-OF functions which actually do return the maximum and minimum values (see #1972 for such a proposal).
Normally this would be against the (defacto) legacy naming rules, but we make an exception for functions that are rarely used and really badly named, especially when we have a much better use for the name. MAXIMUM-OF and MINIMUM-OF fit that description.
This issue was last mentioned in #1818, but was first brought up in AltME years ago. See also #428 for issues that relate to /skip behavior of these functions.
Imported from: CureCode [ Version: r3 master Type: Wish Platform: All Category: Mezzanine Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#1971
Comments:
Submitted by: BrianH
Ch.Ensel (aka ChristianE) suggested that these be named AT-MAXIMUM and AT-MINIMUM instead in #1818. However, the functions don't really seem related to AT. For AT, you already know and specify the position; for these functions, you are trying to find the position. These really seem like they're more related to FIND.
Submitted by: Gregg
I agree with this change. From the old AltMe chat on it, Ladislav was against it, but suggested doc string changes would help. Here were my proposals at that time:
FIND: "Returns the series where the value is found, or none if the value is not found."
FIND-MAX: "Returns the series where the largest value is found, or none if the series is empty."
AT-MAX: "Returns the series at the position where largest value is found, or none if the series is empty."
AT-MAX: "Returns the series at the largest value, or none if the series is empty."
I still prefer the FIND* variant over AT*, but either is better than what we have now.
Submitted by: BrianH
Requested Oldes/Rebol-wishes#58 to be better able to implement functions like these with the #428 record comparison rules.
The text was updated successfully, but these errors were encountered: