Changes between Version 20 and Version 21 of Ticket #13072
 Timestamp:
 09/12/12 01:00:49 (8 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

Ticket #13072 – Description
v20 v21 1 1 This patch implements the following classes: 2 2 3 * PartitionTuple  returns a tuple of partitions4 * PartitionTuples  factory class for all tuples of partitions5 * PartitionTuples_level  class of all tuples of partition of a fixed level6 * PartitionTuples_size  class of all tuples of partition of a fixed size7 * PartitionTuples_level_size  class of all tuples of partition of a fixed level and size. The first three of these are infinite enumerated classes whereas the last is finite. They all have iterators.3 * !PartitionTuple  returns a tuple of partitions 4 * !PartitionTuples  factory class for all tuples of partitions 5 * !PartitionTuples_level  class of all tuples of partition of a fixed level 6 * !PartitionTuples_size  class of all tuples of partition of a fixed size 7 * !PartitionTuples_level_size  class of all tuples of partition of a fixed level and size. The first three of these are infinite enumerated classes whereas the last is finite. They all have iterators. 8 8 9 The idea is to implement a fully function class for PartitionTuples as I currently need this together with a class for tuples of (standard) tableaux (coming soon).9 The idea is to implement a fully function class for !PartitionTuples as I currently need this together with a class for tuples of (standard) tableaux (coming soon). 10 10 11 PartitionTuples of level 1 are in natural bijection with Partitions so when given a 1tuple of partitions, or a partition, PartitionTuples() returns the corresponding Partition. This works almost seamlessly, making it possible to almost ignore the distinction between Partitions() andPartitionTuples(). One exception is that the expected behaviour of11 !PartitionTuples of level 1 are in natural bijection with Partitions so when given a 1tuple of partitions, or a partition, !PartitionTuples() returns the corresponding Partition. This works almost seamlessly, making it possible to almost ignore the distinction between Partitions() and !PartitionTuples(). One exception is that the expected behaviour of 12 12 13 13 {{{