On Thursday, April 1, 2021 at 7:38:57 AM UTC-5 Edward K. Ream wrote: If I were designing Leo's Position class today, I would eliminate or hide > the p.moveTo* methods, the p.copy method, and the copy kwarg for all of > Leo's generators. These changes would make positions immutable. >
These changes would also eliminate all tests of the form `if p` or `if not p` and would moot the assignment p.v = None in various moveTo* methods. Again, I am unlikely ever to *prohibit* tests on p. There is not nearly enough reason to break existing user scripts. Instead, within Leo's core, I'll adopt the *attitude* that positions should be treated as immutable. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/57276df0-2aeb-47de-a58d-4cfc630f2c0dn%40googlegroups.com.
