Talk:McNuggets problem: Difference between revisions
m
Thundergnat moved page Talk:McNuggets Problem to Talk:McNuggets problem: Follow normal task title capitalization policy
(→Python: "composing generic abstractions": Whoops?) |
Thundergnat (talk | contribs) m (Thundergnat moved page Talk:McNuggets Problem to Talk:McNuggets problem: Follow normal task title capitalization policy) |
||
| (2 intermediate revisions by 2 users not shown) | |||
Line 19:
I would not have restricted the high limit to '''100''', but left that open-ended (in other words, infinity).
It would also get around the use of a trade-marked (TM or ™) term(s) and also a registered (R or ®) trade-mark term, but it seems that Wikipedia skipped around those problems. &
==Python: "composing generic abstractions"==
Line 33 ⟶ 32:
: paddy Well, I suppose one 'use' is that it does have a style. The examples now under REPL import functional idioms from itertools and abuse them in some sort of style chimera. Somewhere in this discussion you complained about the use of functional idioms rather than the pythonic Comprehensions. These were introduced in Python2 and the What's New in Python2 documentation explains in length how to map one to the other. Why then when I write a solution importing nothing and using only Comprehensions do you denigrate it as 'From F#'. Surley this is the Pythonic Solution--[[User:Nigel Galloway|Nigel Galloway]] ([[User talk:Nigel Galloway|talk]]) 14:08, 29 October 2018 (UTC)
:: Hi Nigel;
| |||