Pondering my visual functional "Alonzo" programming language...
1. I realized that I neglected to include anywhere to document types. I should include a field for that!
Now should that be a localized string or an expression? I suppose if I want to expose this documentation as tooltips it should be short-ish strings...
2. Its tempting to have drawing lines between different slots in a pattern denote equality, but once I include callbacks not everything can be compared...
1/2!
2 (cont). I suppose clicking a generic parameter could toggle whether or not it should be type that supports equality checks.
3. I've got internationalization of any function name, & in turn any UI component you might write in Alonzo. Maybe should have a built-in type for internationalized strings?
These would hold one string per locale & render as the string for your locale, where available. This could be nice for documentation comments?
2/2!