From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id F357F1F5AE for ; Thu, 23 Jul 2020 18:20:03 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 6BDC3120B4E; Fri, 24 Jul 2020 03:19:30 +0900 (JST) Received: from xtrwkhkc.outbound-mail.sendgrid.net (xtrwkhkc.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 8E1EC120B4C for ; Fri, 24 Jul 2020 03:19:28 +0900 (JST) Received: by filterdrecv-p3iad2-5b55dcd864-hp5f5 with SMTP id filterdrecv-p3iad2-5b55dcd864-hp5f5-19-5F19D4CA-27 2020-07-23 18:19:54.351894769 +0000 UTC m=+2337032.395322788 Received: from herokuapp.com (unknown) by ismtpd0021p1iad2.sendgrid.net (SG) with ESMTP id VeL_ZW-bSJeGNGJ3YoJlqw for ; Thu, 23 Jul 2020 18:19:54.260 +0000 (UTC) Date: Thu, 23 Jul 2020 18:19:54 +0000 (UTC) From: contact@delonnewman.name Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 75091 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Feature X-Redmine-Issue-Id: 17043 X-Redmine-Issue-Author: delonnewman X-Redmine-Sender: delonnewman X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: =?us-ascii?Q?gNS39Mfls23T6mUd1od9trNVAZHJrxR668BMAgjsmX8IgHAm1JsLe1o43AiAhM?= =?us-ascii?Q?1o=2FP8y8PwaQs+tg8cHcNWBKQZcl2+LeuvLuPW5V?= =?us-ascii?Q?a2lSCsSwZ1Y85QPo3X+FPi2avbDjGI3foQz9YRa?= =?us-ascii?Q?budubFkHR+LNJgPS9HXOtZy0WRly5IZdE56rIUS?= =?us-ascii?Q?+qXGrABv787aUSBn2V4ZJmzKqc07hm6Vlyz0wMR?= =?us-ascii?Q?AbEx4kOH56xjl8dww=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 99302 Subject: [ruby-core:99302] [Ruby master Feature#17043] Invokable module for custom Proc-like objects X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #17043 has been updated by delonnewman (Delon Newman). Yeah, I guess I wasn't as clear. I'm curious if an officially blessed "Invokable" module might be a useful thing for the standard library. I obviously don't have the perspective you do. ---------------------------------------- Feature #17043: Invokable module for custom Proc-like objects https://bugs.ruby-lang.org/issues/17043#change-86690 * Author: delonnewman (Delon Newman) * Status: Feedback * Priority: Normal ---------------------------------------- Ruby beautifully integrates Functional and Object-Oriented Programming, and there's more moving in the direction of supporting Functional Programming. A generalization of the Proc interface would enable users to integrate functional approach into their classic OOP design patterns. One of the obvious examples would be "Command" objects. Also, generic structures, which Ruby has great support for. Hash now has `to_proc`. But, it'd be great to be able to treat sets as predicate functions. I've put together a prototype that I've found useful in my own work here: https://github.com/delonnewman/invokable. It works like Enumerable; it can be included in any class that implements a `call` method. Then you get `to_proc`, `curry`, `<<` and `>>` for right and left composition, and `memoize`. More could be added. If you include `Invokable::Command`, you can treat your "Command" object as an automatically curried function. -- https://bugs.ruby-lang.org/