Talk:McNuggets problem: Difference between revisions
→Python: "composing generic abstractions"
(/* Python: functional programming is one of the ways in which Python interpreters and compilers are used. No need to delete.) |
|||
Line 29:
:: The point is to demonstrate functional uses of Python, on which there is an established literature, and which meets the needs of particular contexts. If it resembles Haskell to you, that is because all functional programming, with any interpreter or compiler, is mathematically constrained by the same necessities of functional composition, and this leads to common use, across many languages, of shared generic abstractions.
::By default, names for these abstractions tend to be taken, in many languages, including Python, from the Haskell/ML tradition, which simply happens to be the main idiom of the academic research in functional programming. The name of Python's '''dropwhile''' function is an example, as explained at the top of the Python itertools module documentation.
::You can safely leave it alone. No need for deletionary zeal. Like it or not, functional programming is one of the ways in which Python interpreters and compilers are used. Live and let live. I have absolutely no objection whatsoever to other styles of programming. What is good depends entirely on what we are optimising for, and in what context, and what is meant by 'idiomatic' is best left to linter tools. This code is fully linted by AutoPep8 and Auto-flake8. That seems enough to me. [[User:Hout|Hout]] ([[User talk:Hout|talk]]) 08:15, 27 October 2018 (UTC)
| |||