I updated the ForeignBlocking wiki page with what I believe is the
current state of this proposal; see

didn't I mention that "concurrent" may be inappropriate and misleading, and that I think it is bad practice to rely on the programmer annotating the dangerous cases, instead of the safe cases?

wouldn't the safe approach be to assume that the foreign call may do anything, unless the programmer explicitly tells you about what things it won't do (thus taking responsibility).

cheers,
claus

http://haskell.galois.com/cgi-bin/haskell-prime/trac.cgi/wiki/ForeignBlocking

_______________________________________________
Haskell-prime mailing list
Haskell-prime@haskell.org
http://haskell.org/mailman/listinfo/haskell-prime

Reply via email to