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

EEP-55's Backwards Compatibility #19

Closed
paulo-ferraz-oliveira opened this issue Jan 16, 2021 · 1 comment
Closed

EEP-55's Backwards Compatibility #19

paulo-ferraz-oliveira opened this issue Jan 16, 2021 · 1 comment

Comments

@paulo-ferraz-oliveira
Copy link

This is more of a question/request for guidance that an issue.

EEP-55's Backwards Compatibility seems to refer to using old code on an Erlang/OTP version that already supports the pinning operator (e.g. OTP 24, 25, ...).

I'm wondering how we'd be able to use new code that uses it in older Erlang/OTP-supported software (e.g. OTP 19, 20, ...). Would a parse transform of any kind be possible, here?

Thanks.

@garazdawi
Copy link
Contributor

Hello!

This is a question better asked of the EEP author, so take this to the mailing list or the PR associated with the EEP.

Lukas

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

2 participants