I don't think a Haskeller should try to use point-free code. It's just that if you're refactoring your code and you get it down to the point that you've got
thing x = th . in . g x
you might as well finish the job and take the x out. What's left should make sense to you if you follow this process and just let it happen. But I feel no shame when I can't go pointfree, especially when pointfree requires crazy hacks to simulate a simple pattern match.Sorry, but, aside from the obviously unimportant use of `in` (a reserved word), this gives a different type from what I think you meant:
x :: a
g :: a -> b -> c
in :: c -> d
th :: d -> e
thing :: a -> b -> e
and naïve eta-conversion will give you something that isn't well typed. Probably you meant thing x = th . in . g $ xYes, thanks.
They should have told you write f = (x -> x^2) or so.
I think it's better pedagogically just to acknowledge that, in common mathematical discourse, "the squaring function" doesn't have any symbolic name. Perhaps it's more illustrative to think of, for example, `f(x) = ln(x)` (the value of a function) versus `f = ln` (the function itself); and a good (college) mathematics teacher will make this distinction.
Re:Pointfree style in Python
by perfunctory on Tuesday November 15, 2011 @03:19AM
(#3237512)
They could also tell me to write (= f (-> (x) (^ x 2))). Then we would all be using lisp and laughing and those few developers who would using that weird infix notation.
While I like S-Expressions for computers, even in that small example the parenthesis are a bit excessive. Keep in mind that mathematics is mostly written by hand on a black board.
Ah, so it's postfix you want?
fxx2^1+→=
:-)
EDIT: That is, all these years at school I was taught to write f(x) = x^2, not f = (^2).