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

Consider including Fe in the spec #26

Open
cameel opened this issue Apr 19, 2023 · 0 comments
Open

Consider including Fe in the spec #26

cameel opened this issue Apr 19, 2023 · 0 comments

Comments

@cameel
Copy link
Contributor

cameel commented Apr 19, 2023

Currently the spec is based only on existing Solidity and Vyper features:

In addition, this proposal is necessarily geared towards the state of the Solidity/Vyper languages as they exist now.

I think it may be a good idea to also include Fe in that set. It's still not considered entirely stable but it already went past the alpha stage and will likely be considered one of the major contract languages on the EVM in the future. I mean, there were a few short-lived experimental languages that never gained traction and eventually died off, but this is not one of them.

It already has some features that would potentially future-proof the spec: generics (at least in some limited version), proper tuple types, enums with data.

Alternatively, it should be considered for inclusion in future versions if we prefer to exclude it from the initial one to limit the scope, but I wanted to make sure everyone is aware it exists.

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