When programming, you may struggle to find coherent meaningful names and types, given conflicting alternatives, metaphors and styles suggested by many previous APIs in many languages or by scientific literature. Or you may just pick the first thing that comes to mind.
An improvement would be the macro suggesting a valid replacement form, instead of just referring the user to the documentation.
-
-
But interesting cases are non-local, at which point you really want module-wide macro-expansion control in the style of PLT Racket. Or, further, repository-wide cross-file analysis with caller and callee tracking.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!