For FP does this mean that lots of methods must involve a switch based on Type? How well will this work in Elan?
We definitely need pattern matching
Can we do this for asString() ? In which case can we say that a class does not have to have an asString. Note that it might still be useful to force the user to think about asString, by including the method (modifiable) in the Frame. but perhaps not for immutable class (likely to be used most in FP).
For FP does this mean that lots of methods must involve a switch based on Type? How well will this work in Elan?
We definitely need pattern matching
Can we do this for
asString()
? In which case can we say that a class does not have to have anasString
. Note that it might still be useful to force the user to think about asString, by including the method (modifiable) in the Frame. but perhaps not forimmutable class
(likely to be used most in FP).