Next steps for Leo

47 views

Skip to first unread message

Edward K. Ream

unread,

Apr 2, 2024, 5:41:15 AM4/2/24

to leo-editor

Here are my expectations and plans as I gradually resume work after eye surgery.

- LeoInteg 1.0.20 contains significant UI improvements. I expect Félix will fold those improvements into LeoJS. That work shouldn't take too long, but that doesn't mean that LeoJS 1.0.0 will happen imminently.

- I created piles of Post-it notes while convalescing. I'll be editing those notes soon. Some ideas are likely rubbish, but others seem promising. Stay tuned.

- Creating better annotations for Leo's methods will continue after PR #3850. Another post will discuss annotations in more detail.

- Last month, I had a game-changing Aha about type-checking. It is much easier than I ever imagined. I'll say more in another post.

- Yesterday, I had an Aha about annotations. Roughly speaking (I have yet to check the details in the mypy docs), the Aha is this: The "Union" annotation requires that all attributes (of the annotated names) exist in the intersection of the classes in the union. This Aha resolves several other mysteries that confused me. I'll say more later as needed.

Summary

Work on Leo is far from over :-)

Better annotations will help devs maintain Leo's codebase--both now and after I am gone. In particular, requiring "strict optional" typing should significantly strengthen Leo's annotations.