Talk:Cheryl's birthday: Difference between revisions
→Improve tag on Python entry
mNo edit summary |
|||
Line 34:
Composition of pure functions is not going to go away. Time, math, and multiprocessors are all on its side. As for 'idiomatic', with functional code, that maps not to the deliberately functional-dsyfunctional 'Pythonic' verities, but to the standard use of standard functional abstractions, with names taken, by default, from the very same idiom as Python's takewhile, dropwhile and groupby etc [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 11:16, 26 October 2018 (UTC)
: PS Imperative coding seldom works well in my context, tho I sometimes use it at a latish stage if I happen to need to trade away some reliability to gain a bit of compression (a bit like JPEG in lieu of PNG), but I have absolutely no objection at all to others working with it. Rather than slapping banning orders on functional drafts that you fear might differ from the
| |||