From: shevegen@... Date: 2019-10-18T13:58:00+00:00 Subject: [ruby-core:95422] [Ruby master Feature#16261] Enumerable#each_tuple Issue #16261 has been updated by shevegen (Robert A. Heiler). Hmmmm. A slight issue I see with the name "tuple", and then the implicit name addition ".each_tuple", which would then (indirectly) elevate the term tuple. I know the word tuple from e. g. using tuple in python, but I much prefer ruby's way to name things (not only because I used ruby for a longer time than python, but because I think the names in ruby make more sense in general e. g. Array/Hashes versus List/Dictionaries). I am not sure if we have "tuples" in ruby core/stdlib yet. I did however google and find it in Rinda ... so at the least Rinda in stdlib has tuples. :P https://ruby-doc.org/stdlib-2.6.5/libdoc/rinda/rdoc/Rinda/Tuple.html (Not sure about ruby core, though.) There is also a slight issue with intrinsic complexity (in my opinion), but this is a lot due to one's personal style and preferences, so I will not comment much on that part - some ruby users prefer simplicity, others prefer more flexibility in usage (aka more complex use cases). But I think the name itself should be considered as well; for the use of .each_tuple, ruby users would first have to understand what a tuple is. Compare this to e. g. .each_pair which is a LOT simpler to understand even to genuinely new people. I also admit that this is not a very strong argument per se, since we have other variants of .each* already, such as .each_with_index - but I still think we should be careful which .each* variants are added. I also have no alternative name proposal, my apologies. ---------------------------------------- Feature #16261: Enumerable#each_tuple https://bugs.ruby-lang.org/issues/16261#change-82175 * Author: zverok (Victor Shepelev) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- New method proposal. Prototype code: ```ruby module Enumerable def each_tuple return to_enum(__method__) unless block_given? each { |item| yield(*item) } # unpacking possible array into several args end end ``` Supposed documentation/explanation: > For enumerable with Array items, passes all items in the block provided as a separate arguments. t could be useful if the provided block has lambda semantics, e.g. doesn't unpack arguments automatically. For example: ```ruby files = ["README.md", "LICENSE.txt", "Contributing.md"] content = [fetch_readme, fetch_license, fetch_contributing] # somehow make a content for the files files.zip(content).each_tuple(&File.:write) # writes to each file its content ``` > When no block passed, returns enumerator of the tuples: ```ruby [1, 2, 3].zip([4, 5, 6]).each_tuple.map(&:+) # => [5, 7, 9] ``` -- https://bugs.ruby-lang.org/ Unsubscribe: