Changes between Version 1 and Version 2 of Ticket #10963, comment 313
- Timestamp:
- 01/07/14 11:13:01 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #10963, comment 313
v1 v2 6 6 infrastructure is acceptable if it avoids redundancy in many places in 7 7 the code using that infrastructure. Trading uglyness in one spot for 8 beauty in many. For example ClasscallMetaclassis definitely ugly8 beauty in many. For example `ClasscallMetaclass` is definitely ugly 9 9 black magic, but I believe it was the price to pay for the nice 10 UniqueRepresentationidiom.10 `UniqueRepresentation` idiom. 11 11 12 12 Now, in the case at hand, is this going overboard?