On Mon, Apr 19, 2010 at 02:57:00PM +0100, Simon Marlow wrote:
> A few of the tests in the test suite assume a UTF-8 locale, so you're
> probably falling foul of that. We could fix the tests - but we do want
> to test that the locale encoding is being respected in some way, so just
> adding hSet
On 18/04/2010 19:22, Matthias Kilian wrote:
Hi,
On Sun, Apr 18, 2010 at 10:53:22AM -0700, Judah Jacobson wrote:
Anyway, the short story is that I have to either hard-code the
character set to something like utf-8, or ghc will start to behave
really strange (for example, ghci would terminate imm
On 18/04/2010 10:28, Denys Rtveliashvili wrote:
While alloca is not as cheap as, say, C's alloca, you should find that
it is much quicker than C's malloc. I'm sure there's room for
optimisation if it's critical for you. There may well be low-hanging
fruit: take a look at the Core for alloca.
On 15/04/2010 18:12, Yitzchak Gale wrote:
My opinion is that we should either use TWO DOT LEADER,
or just leave it as it is now, two FULL STOP characters.
Just to be clear, you're suggesting *removing* the Unicode alternative
for '..' from GHC's UnicodeSyntax extension?
I have no strong opin
| >> I compiled my code with -fdicts-strict.
| >
| > What is this actually supposed to do? It seems the documentation is
| missing:
| > http://www.haskell.org/ghc/docs/latest/html/users_guide/options-
| optimise.html#options-f
|
| >From reading the source code, it appears to make any dictionary fi
