Re:Frege: A JVM pure functional programming language in the ...
by Tyr42 on Thursday November 07, 2013 @09:31AM
(#6689470)
I like some of the differences where it was not constrained by Haskell's choices, like splitting up the Monad, Applicative, Functor instances, and namespacing of accessors.
I also quite like the • for compose, with then some shims so that . works too if it's not being used for the namespacing.
[ Parent
| on HN ]
Re:Frege: A JVM pure functional programming language in the ...
by anon_d on Thursday November 07, 2013 @03:50PM
(#6692283)
Yeah, I'd like to see more languages using unicode identifiers. Seems to be a very unpopular approach, though :(
Re:Frege: A JVM pure functional programming language in the ...
by tikhonj on Thursday November 07, 2013 @07:56PM
(#6693700)
Haskell can do it: there's a library with common Unicode operators[1] (including ∘ for function composition) and an extension allowing you to use Unicode syntax[2] (things like → in place of ->).
I've seen these things used, but they're not super common. People still worry about not being able to input Unicode symbols in their editor! I personally think this is absurd in this day and age. Naturally, it's very easy to do in Emacs; somebody even wrote a Haskell input mode[3].
[1]: http://hackage.haskell.org/package/base-unicode-symbols-0.2....
[2]: http://www.haskell.org/ghc/docs/7.2.1/html/users_guide/synta...
[3]: https://github.com/roelvandijk/emacs-haskell-unicode-input-m...
Re:Frege: A JVM pure functional programming language in the ...
by anon_d on Sunday November 10, 2013 @01:11AM
(#6705499)
Oh, nice! I setup XCompose to support rfc1345, so I have fast unicode input everywhere. I'm definitely going to experiment with that Haskell extension. I've done that manually before in ML with a preprocessor, but it was a nasty hack. A proper extension is much nicer!
EDIT: How many people still have trouble with Unicode input? Should I publish my XCompose solution?
Re:Frege: A JVM pure functional programming language in the ...
by voxfrege on Thursday November 07, 2013 @04:57PM
(#6692704)
It turned out that porting Haskell code was a nightmare when the (.) did not work yet. (You can't just replace each . with • unless you don't have any qualifed names.)
Today, it can be quite easy, in the best case you just Ctrl-C Ctrl-V