Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Redefine capture avoiding substitution recursively #5

Open
chrisbanks opened this issue Feb 2, 2012 · 0 comments
Open

Redefine capture avoiding substitution recursively #5

chrisbanks opened this issue Feb 2, 2012 · 0 comments

Comments

@chrisbanks
Copy link
Owner

Capture avoiding substitution needs redefining.

Note from Ian:
"The possible questions on the alpha-conversion are to do with you having an implementation working almost entirely at the top level, rather than recursively down the structure of terms. All of the detailed operations are done recursively, of course --- free names, bound names, renaming --- but the strategy for capture avoidance is to call each of those from the top level, rather than, say, define capture-avoiding renaming directly by recursion. I think it's safe, but there are some curiosities. For example, when a name appears in a term both bound and free, in different subterms."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant