> no basic knowledge how JavaScript is interpreted at runtime Could you show where author wrong about this?
http://lambdacube3d.com/editor.html why type inference (for hints in editor) is so cool? Can I do something similar for haskell (without pain if possible)?
Is it only proof of concept? If no: How they develop compiler to language with incomplete spec?
tell me about message passing without concurrency. is it message passing in ruby? and why.
> prefixes, default instances Also bad setters ("record {field = val}" looks nice but useless, as not a function). I hope the developers of GHC also clearly see the problem and someday will be engaged in it. Then the…
I'm not good enough haskell programmer, but there is possible solution (records as you mentioned). import Prelude hiding ((-)) data Grep = Grep {isRecursive :: Bool, maxCount :: Maybe Int} --etc deriving (Show) grep =…
> no basic knowledge how JavaScript is interpreted at runtime Could you show where author wrong about this?
http://lambdacube3d.com/editor.html why type inference (for hints in editor) is so cool? Can I do something similar for haskell (without pain if possible)?
Is it only proof of concept? If no: How they develop compiler to language with incomplete spec?
tell me about message passing without concurrency. is it message passing in ruby? and why.
> prefixes, default instances Also bad setters ("record {field = val}" looks nice but useless, as not a function). I hope the developers of GHC also clearly see the problem and someday will be engaged in it. Then the…
I'm not good enough haskell programmer, but there is possible solution (records as you mentioned). import Prelude hiding ((-)) data Grep = Grep {isRecursive :: Bool, maxCount :: Maybe Int} --etc deriving (Show) grep =…