Re:Some thoughts on asynchronous Python API design in a post...
by rtpg on Monday November 07, 2016 @12:13AM
(#12888953)
well that's kind of the point isn't it? That Python doesn't offer this, and that Haskell is one of the few production-ready tools that offer this in a clean way?
Re:Some thoughts on asynchronous Python API design in a post...
by quotemstr on Monday November 07, 2016 @12:17AM
(#12888972)
Who cares how it's implemented? Python lets you write straight-line code that does more than one IO-bound thing at a time. So does Haskell. That one is using a CPS transform under the hood and the other stack-switching via OS threads is irrelevant.
Re:Some thoughts on asynchronous Python API design in a post...
by rtpg on Monday November 07, 2016 @03:56AM
(#12889721)
it's not exactly the same. Python lets you write straight-line code, but you still have to be explicit about the sync/async nature of each call. You can abstract this away in Haskell, thanks to some interesting tooling around `do` notation. Some people prefer the explicit nature though.
You can do that in any language with AST transforms powerful enough to transform code into CPS. That functions are "automatically callbackified" is an implementation detail and not one particularly germane to high-level code.