> I don't think it's so much bugs as it's funky indentation :-). For
> example...
> data TableInfo = TableInfo {
> avgPot :: Double,
> I would have preferred not to offset the fields from the brace but I don't
> know how to change this and maybe I'm going against stan
>> You mean you'd like
>>
>> data TableInfo = TableInfo {
>>avgPot :: Double,
> No, I would actually like to offset avgPot 4 spaces from TableInfo.
In that case I'm with you. It's on my wish list as well.
>> which is much better. I'd personally prefer
>>
>> case f
> Can I throw a vote in for handling
> data T = T { granularity :: (Int, Int, Int, Int)
> , items :: Map (Int, Int, Int, Int) [Item] }
> correctly? That (and case statements) are the only things that really
> still bother me about haskell-mode.
AFAIK this is handled correctly in th
Simon Marlow wrote:
$ ghc -v
Glasgow Haskell Compiler, Version 6.4, for Haskell 98, compiled by GHC
Please try again with 6.4.1; lots of bugs were fixed.
Stupid me. I could swear I upgraded, but in fact did not.
Checked with 6.4.1, works as expected, thanks.
BTW: Does anybody have binary v
Is "with" better than allocaBytes?
On Oct 22, 2005, at 12:42 AM, John Meacham wrote:
because haskell values don't have the same representation as C values.
haskell values are pointers to updatable thunks. in any case 'with'
just allocates 4 bytes on the stack (the same as a auto C declaration)
