User talk:Tiddlywinks/Archive 1: Difference between revisions

m
Line 1,391: Line 1,391:
Actually, you were talking about unique type combinations at that point. You said "Instead of including every permutation (of type combinations - of which there are 324), this list only includes type combinations." It makes no sense as you are not specifying whether or not the list includes all or just unique type combinations. Adding unique before specified that the list makes no distinction between a shared type combination in a different order. {{unsigned|Disgraced}}
Actually, you were talking about unique type combinations at that point. You said "Instead of including every permutation (of type combinations - of which there are 324), this list only includes type combinations." It makes no sense as you are not specifying whether or not the list includes all or just unique type combinations. Adding unique before specified that the list makes no distinction between a shared type combination in a different order. {{unsigned|Disgraced}}
:Oh, I'm sorry, I got confused by the existence of [[List of Pokémon with unique type combinations|this page]]. But besides that, a {{wp|combination (disambiguation)|combination}} by definition makes no distinction based on order. The explicit difference between combinations and permutations is that permutations take order into account while combinations do not. "Unique" is still an unnecessary qualifier. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 13:00, 14 August 2014 (UTC)
:Oh, I'm sorry, I got confused by the existence of [[List of Pokémon with unique type combinations|this page]]. But besides that, a {{wp|combination (disambiguation)|combination}} by definition makes no distinction based on order. The explicit difference between combinations and permutations is that permutations take order into account while combinations do not. "Unique" is still an unnecessary qualifier. [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 13:00, 14 August 2014 (UTC)
That page is using unique in a different context. That page refers to ''pokemon'' who are unique in their typing. The page we're talking about is using unique to describe that to two tables make no distinction between type combinations of a different order. By saying it includes 171 unique type combinations of the possible 324, it implies that, for example, ghost/dark and dark/ghost are considered ''one'' unique type combination.
25

edits