Edwin Brady dbdf7dab3d Back to HasIO, remove MonadIO ... Following a fairly detailed discussion on slack, the feeling is generally that it's better to have a single interface. While precision is nice, it doesn't appear to buy us anything here. If that turns out to be wrong, or limiting somehow, we can revisit it later. Also: - it's easier for backend authors if the type of IO operations is slightly less restrictive. For example, if it's in HasIO, that limits alternative implementations, which might be awkward for some alternative back ends. - it's one less extra detail to learn. This is minor, but there needs to be a clear advantage if there's more detail to learn. - It is difficult to think of an underlying type that can't have a Monad instance (I have personally never encountered one - if they turns out to exist, again, we can revisit!)		2020-06-21 19:21:22 +01:00
..
casetot.idr	Calculate compile time references even in case	2020-05-30 21:53:29 +01:00
expected	Back to HasIO, remove MonadIO	2020-06-21 19:21:22 +01:00
run	Calculate compile time references even in case	2020-05-30 21:53:29 +01:00