Effekt Language: Home
15 points by napkindrawing
15 points by napkindrawing
It’s good that they’re exploring and documenting alternatives to having effects as type parameters in function types, but the downside of this design is pretty big: you have to give up on first-class functions.
I wrote some of my thoughts on Effekt’s solution to the problems with representing effects of functions as a type parameter here.
It’s good that they’re exploring and documenting alternatives to having effects as type parameters in function types, but the downside of this design is pretty big: you have to give up on first-class functions.
Effekt has added support for first-class functions a few years ago (in 2022), so you no longer have to give them up – although functions (and comparisons in general) in Effekt are second-class by default, they can be first-class if you want them to be. See for example the scheduler case study, some sections in the tutorial relating to this (captures, computation), or a related paper.
Thanks, didn’t know that there was an update to the type system in the 2020 paper. I’ll have a look at the 2022 paper.
Yes, the language changes a lot. We have a language evolution page that explains the changes over the years.