On 11/29/16 4:04 AM, Mike Zabrocki wrote:
> I agree that the two methods should not have the same name.
> My suggestion: deprecate one and call it 'to_word_by_column_reverse'
> (although it seems weird to bother to include both).
>
> Can SkewTableau inherit from Tableau and have 'to_word_by_colum
I agree that the two methods should not have the same name.
My suggestion: deprecate one and call it 'to_word_by_column_reverse'
(although it seems weird to bother to include both).
Can SkewTableau inherit from Tableau and have 'to_word_by_column' there?
-Mike
On Monday, 28 November 2016 19:05:4
Yes they should definitely be consistent -- sorry, I misread your email and
thought that you wanted the method for skew tableau to be the reverse of
that for tableauxnot enough coffee (or maybe too much:).
As it currently stands there are many independent tableaux classes.
Ideally, methods
Hi Andrew,
If someone had just copied the code from Tableaux to SkewTableaux,
then at least it would be consistent. I think it is really bad,
if a method changes convention with a parent, given that one
could be a subclass of the other.
Best,
Anne
On 11/28/16 1:23 PM, Andrew wrote:
> Hi Anne,
>
Hi Anne,
One of the problems with tableaux is that almost every possible variation
of any definition is used by some one. With this in mind we probably should
implement variations whenever possible. I don't know anything about the
history of this particular method (git blame might help), but I
