Owl has True/False/Null/... in places of #t, #f, '() and other immediates, and
the plan has been to extend this for derived constructors, like (Cons a b),
(Vertex na l nb), ...
This would be, and was mainly planned for, pattern matching to keep the
constructors separate of bindable values.
This is starting to feel like a bad idea. The constructors shadowing could for
example be enforced separately, or one could simply use ((cons a b) ...), check
that cons isn't bound locally, check what the value is at current interaction
environment and then pick the appropriate check and bind.
Original issue reported on code.google.com by aohelin on 15 Jan 2012 at 1:37
Original issue reported on code.google.com by
aohelin
on 15 Jan 2012 at 1:37