j: Next unread message
k: Previous unread message
j a: Jump to all threads
j l: Jump to MailingList overview
The hasattr() tests can be expensive for repeated throwers and senders. Any merit to caching the result of the test?
The expansion is a specification of the semantics, not an implementation.
I would have thought that running hasattr() no more than once is a semantic detail.
Also, speed is a relevant consideration whenever users have the choice of continuing to do things the old way. If the new syntax is slower for key use cases, why would anyone adopt it?