Matthew Lutze
Matthew Lutze
> @mlutze Gagan is using a mutable array, but I think for any kind of backtracking to be feasible we will want a purely functional implementation, right? Yes, agreed. If...
@gaganchandan please ping me when this is ready for another review
> Renamed like you said, got this error now: `Expected an error of type ExceptionTypeMatchError, but found: List(ca.uwaterloo.flix.language.errors.ParseError$UnexpectedToken, ca.uwaterloo.flix.language.errors.ParseError$UnexpectedToken, ca.uwaterloo.flix.language.errors.ParseError$UnexpectedToken)` This indicates there is a parsing error in your tests....
> ``` > def testPriority01(): Bool \ IO = > try { > exception(); > false > } catch { > case _: ##java.lang.Exception => true > case _: ##java.lang.ArithmeticException...
It seems we could express some of these relationships via aliases. Suppose we go ahead and make the tree of subeffects, so we have, e.g., ``` Time
Anything blocking this?
Part of the fix for this would be to detect shadowing of type variables.
> like ```x `put` thing```? More like `x
> A `Ref` is a struct now-ish, so I guess `ref.value = thing` would work Is that part of the interface or is it an implementation detail?
Ref does not implement these since there is no index.