mythryl/mythryl — Issue #3: Best Practices notes/ideas
Author: spiralofhope
Created: 2012-01-22 23:47:37+00:00
State: open

- http://mythryl.org/pipermail/mythryl/2011-October/000482.html
- http://mythryl.org/pipermail/mythryl/2011-October/000488.html

> clarify globally, abbreviate locally

- http://mythryl.org/pipermail/mythryl/2011-November/000569.html

> Incidentally, when you can't figure out what the type of something
> is, a useful trick is often to just declare it as Int or String or
> whatever, compile, and look at the error message: "foo is declared
> Int but actually Sometype". So then you know it is Sometype.

- http://mythryl.org/pipermail/mythryl/2011-November/000576.html

> The best advice I can give on this front is:
> ... (etc)

- http://mythryl.org/pipermail/mythryl/2011-November/000587.html

> Here seeing the bar (a, zot(b), blarg(c))
> line up-front makes the following function definitions
> much easier to follow, whereas the
> ...
> tends be very hard to read because the purpose of bar, zot and blarg
> remains totally mysterious while reading them (especially if the
> author is given to fn names like 'f, g, h ...' or 'sn, bn, sbn, ...' :-);
> they have to be sort of just stuffed undigested in short-term memory
> (where they don't fit) until the
> ...
> line finally arrives and ties it all together.

(etc)