future of smart

[Gustavo Niemeyer]

Hi again Grant,

> My current list

Sounds like a nice list.  I'm looking forward to having anything
from it being actively worked upon.  One thing to keep in mind is
that we need tests for any feature implemented, as Smart works on
several platforms, and the only way to ensure that things continue
to work is to include proper unittests.

When needed, I can answer questions on the basics of unittestings
in case you (or anyone else) would want to.

A few comments for specific entries:

>    3. fewer cache updates especially when nothing was done.

Again, cache updates/saves are only done when they have to be done.
If you think you have cases that don't have to be done, please
include very detailed information to the code level.  This path has
been optimized and profiled extensively, so simply saying "a executed
something and I think the cache didn't need an update" will not be
considered as a proper report.

>    7. Cleaner syntax - sometimes it gets really messy.

That's very vague.  I don't even know what syntax you're talking about.
Please include good examples whenever saying that something is
"really messy", otherwise it's hard to consider the discussion seriously.


Thanks for the consolidated list.

-- 
Gustavo Niemeyer
http://niemeyer.net