12 Commits

Author	SHA1	Message	Date
Kamiλ Shakirov	8e30b296c0	[ refactor ] Remove Data.Strings module (#1607)	2021-06-28 13:48:37 +01:00
Ruslan Feizerakhmanov	51184c156d	[doc] Interface constructors	2021-05-08 11:36:12 +03:00
Raoul Hidalgo Charman	2c8f2483de	Update docs to reflect usage of >> in do syntax	2021-05-01 15:18:49 +01:00
Nil Geisweiller	f390fba766	Rename Sotrable to Storable	2021-02-16 09:51:44 +00:00
Guillaume ALLAIS	5aa4262792	[ fix ] some of the docs	2021-02-10 00:37:06 +00:00
G. Allais	3f6b99e979	[ fix #657 ] RigCount for interface parameters (#808)	2020-12-11 11:58:26 +00:00
Brandon Elam Barker	28cf2a3083	Making "functional dependencies" easier to find	2020-09-30 19:33:02 +01:00
Edwin Brady	950431a9ce	Note in tutorial on qualified do	2020-07-04 23:12:03 +01:00
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
Edwin Brady	1b15463746	Update libraries and docs with HasIO/MonadIO	2020-06-21 15:25:40 +01:00
Milan Kral	9f78f1cddc	replace HTTP links with HTTPS	2020-05-27 14:50:05 +02:00
Edwin Brady	fd55e629ee	Copy more files over from Idris2	2020-05-20 11:23:04 +01:00