3 ms·
By "modulo alpha conversion" I understand you to mean that the functionality was the same, only the names changed in some cases. A clearer way to put this would
by theoh 10y ago
By "modulo alpha conversion" I understand you to mean that the functionality was the same, only the names changed in some cases. A clearer way to put this would be to talk about "equivalence" or maybe even isomorphism?
I'm commenting because the notion of alpha conversion always seems like an inflated idea in the lambda calculus context. Of course \x.x means the same thing as \y.y, no need to make a song and dance about it...
Edit: to add a bit of value, here's Andrew Pitts on the subject:
"The tedious and error-prone nature of ad hoc solutions to this semantically trivial, but pragmatically non-trivial issue of α-equivalence is widely acknowledged"
https://www.cl.cam.ac.uk/~amp12/research/freshml/freshml-final-report.pdf https://www.cl.cam.ac.uk/~amp12/research/freshml/freshml-fin...
(He is talking about programming language support for actually doing metaprogramming jobs that involve preserving alpha equivalence.)
- groovy2shoes 10y agoI disagree that talking about equivalence or isomorphism would be clearer, simply because those two terms are ambiguous. They each have multiple definitions, whereas, as far as I'm aware, alpha conversion only has one. You are correct in your interpretation. I'm not making a song or a dance about alpha conversion, I'm simply using it for description because it is a well-defined notion with a precise meaning. I don't see the point in trying to come up with some other term that means the same thing, when a perfectly good term is already available. Anyway, I appreciate that you are trying to be helpful, but I stand by my phrasing :)