Idris2/libs/base
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
..
Control HasIO interface for IO actions 2020-06-21 01:18:43 +01:00
Data Back to HasIO, remove MonadIO 2020-06-21 19:21:22 +01:00
Debug Add libraries 2020-05-18 14:00:08 +01:00
Decidable Add libraries 2020-05-18 14:00:08 +01:00
Language Reflect 'display names' and record field names 2020-06-07 11:51:09 +01:00
System Back to HasIO, remove MonadIO 2020-06-21 19:21:22 +01:00
base.ipkg Move Data.ST to Control.Monad.ST 2020-06-20 12:51:38 +01:00
Makefile Refactor makefiles 2020-05-19 18:50:47 +06:00
System.idr Back to HasIO, remove MonadIO 2020-06-21 19:21:22 +01:00