[Haskell-cafe] What makes Haskell difficult as .NET?
dmehrtash at gmail.com
Fri May 14 15:14:08 EDT 2010
Would there be issues (lazy evaluation, type system...) with other
languages calling a Haskell code in a hypothetical Haskell in .NET?
On Fri, May 14, 2010 at 10:43 AM, Don Stewart <dons at galois.com> wrote:
> > In this presentation
> > 907
> > the speaker talks about F# on .Net platform. Early on in the talk he
> > that they did F# because haskell would be "hard to make as a .Net
> > Does anyone know what features of Haskell make it difficult as .Net
> The issue here I believe is primarily the desire to interoperate with
> any .NET library, with zero effort by the developer.
> Most .NET libraries are imperative, use mutable state -- so binding to
> those is less fun, and a bit more labor intensive, in Haskell -- though
> the FFI can certainly do it pretty easily.
> It also moves most of the .NET libraries into the IO monad, making them
> less useful.
> -- Don
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe