Timeline for What should a member function be called that applies an argument function to the object?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 12, 2020 at 11:58 | history | edited | jk. | CC BY-SA 4.0 | added 161 characters in body |
| Mar 12, 2020 at 11:35 | comment | added | Flater | @Steve I could contextually understand what "piping the output" means, but like you said, that clarity doesn't extend to "pipe" by itself. | |
| Mar 12, 2020 at 10:25 | history | edited | jk. | CC BY-SA 4.0 | added 76 characters in body |
| Mar 12, 2020 at 8:06 | history | edited | jk. | CC BY-SA 4.0 | added 80 characters in body |
| Mar 12, 2020 at 7:58 | history | edited | jk. | CC BY-SA 4.0 | added 333 characters in body |
| Mar 11, 2020 at 20:36 | comment | added | Steve | I'd say the concept of "piping" the output of one operation to the input of the next is widely understood, and not particular to F#. But I wouldn't recommend the use of the word here. | |
| Mar 11, 2020 at 16:59 | comment | added | Robert Harvey | I'm inclined to agree with @Flater. The word "pipe" in this context is specific to F#. | |
| Mar 11, 2020 at 16:24 | comment | added | jk. | @Flater updated, its not a uniquely F# thing, granted if you havent heard of pipe in any context then it wont mean anything but I think you have to assume some familiarity | |
| Mar 11, 2020 at 16:23 | history | edited | jk. | CC BY-SA 4.0 | added 211 characters in body |
| Mar 11, 2020 at 14:19 | comment | added | Flater | That name would confuse (or not mean anything to) anyone not familiar with F# though. | |
| Mar 11, 2020 at 11:53 | history | answered | jk. | CC BY-SA 4.0 |