4 ms·

Thanks, but that's not enough. The error seems due to the fact that `meter` is passed as an argument to `1` which is not a function, and indeed I don't see how

Thanks, but that's not enough. The error seems due to the fact that `meter` is passed as an argument to `1` which is not a function, and indeed I don't see how that could be valid haskell code (unless there's some language flag I should enable, but unfortunately the wiki/docs of unittyped doesn't seem to be comprehensive enough)

gizmo686 12y ago
Weird, it is enough on my machine (running ghc 7.6.3, unittyped 0.1), but unittyped does seem to use a lot of language extensions internally, it is seems possible that it would behave weirdly on different versions. To answer the question of how it is possible, we can start by looking at the types. ":t" is a ghci command to show the type of an expression: ghci> :t 1 1 :: Num a => a This indicates that "1" can be any type that implements the "Num" typeclass. Next, we want to determine what type "1" takes in the expression "1 meter". We can do this with: ghci> let a=1; b=a meter ghci> :t a a :: UnitTyped.Value Double LengthDimension Meter -> UnitTyped.Value Double ('UnitTyped.UnitCons * Length ('UnitTyped.Pos 'UnitTyped.One) 'UnitTyped.UnitNil) Meter We can see that, in the expression "1 meter", "1" is actually a function. Looking at the source code [1], it seems like this is accomplished in a relativly hacky manner: instance (Fractional f, Convertable a b, t ~ Value f a b) => (Prelude.Num (Value f a b -> t)) where fromInteger i x = Prelude.fromInteger i . x (+) = error "This should not happen" (*) = error "This should not happen" abs = error "This should not happen" signum = error "This should not happen" This works because the "+" being defined here is Prelude.+, not UnitTyped.NoPrelude.+ (which is defined seperatly). [1] https://hackage.haskell.org/package/unittyped-0.1/docs/src/UnitTyped-NoPrelude.htm https://hackage.haskell.org/package/unittyped-0.1/docs/src/U...
- berdario 12y ago
  I see. I tried to report this as a bug, fwiw: https://bitbucket.org/xnyhps/haskell-unittyped/issue/3/num-instance-isnt-imported https://bitbucket.org/xnyhps/haskell-unittyped/issue/3/num-i... Btw, it's weird... I just tried ack-grep "Num\b" and I cannot see any instance of Num defined anywhere inside unittyped's src PS: ok, since I wanted to see exactly what was the problem with unittyped compiling under ghc7.8 I cloned the sources, but I forgot to checkout the actual release... thus running directly from tip was the cause Installing it directly from hackage solved it, it's embarrassing how I was stunned by this in hindsight
tel 12y ago
1 absolutely could be a function—all you need is a function type to instantiate Num.

gizmo686 12y ago

Weird, it is enough on my machine (running ghc 7.6.3, unittyped 0.1), but unittyped does seem to use a lot of language extensions internally, it is seems possible that it would behave weirdly on different versions. To answer the question of how it is possible, we can start by looking at the types. ":t" is a ghci command to show the type of an expression: ghci> :t 1 1 :: Num a => a This indicates that "1" can be any type that implements the "Num" typeclass. Next, we want to determine what type "1" takes in the expression "1 meter". We can do this with: ghci> let a=1; b=a meter ghci> :t a a :: UnitTyped.Value Double LengthDimension Meter -> UnitTyped.Value Double ('UnitTyped.UnitCons * Length ('UnitTyped.Pos 'UnitTyped.One) 'UnitTyped.UnitNil) Meter We can see that, in the expression "1 meter", "1" is actually a function. Looking at the source code [1], it seems like this is accomplished in a relativly hacky manner: instance (Fractional f, Convertable a b, t ~ Value f a b) => (Prelude.Num (Value f a b -> t)) where fromInteger i x = Prelude.fromInteger i . x (+) = error "This should not happen" (*) = error "This should not happen" abs = error "This should not happen" signum = error "This should not happen" This works because the "+" being defined here is Prelude.+, not UnitTyped.NoPrelude.+ (which is defined seperatly). [1] https://hackage.haskell.org/package/unittyped-0.1/docs/src/UnitTyped-NoPrelude.htm https://hackage.haskell.org/package/unittyped-0.1/docs/src/U...

berdario 12y ago
I see. I tried to report this as a bug, fwiw: https://bitbucket.org/xnyhps/haskell-unittyped/issue/3/num-instance-isnt-imported https://bitbucket.org/xnyhps/haskell-unittyped/issue/3/num-i... Btw, it's weird... I just tried ack-grep "Num\b" and I cannot see any instance of Num defined anywhere inside unittyped's src PS: ok, since I wanted to see exactly what was the problem with unittyped compiling under ghc7.8 I cloned the sources, but I forgot to checkout the actual release... thus running directly from tip was the cause Installing it directly from hackage solved it, it's embarrassing how I was stunned by this in hindsight

tel 12y ago

1 absolutely could be a function—all you need is a function type to instantiate Num.