QPQ-AG/sophia
10
0
Fork 0
Code Issues 41 Pull Requests 5 Actions Packages Projects Releases 16 Wiki Activity

Properly deprecate AEVM backend #226

New Issue
Closed
opened 2020-02-18 22:52:01 +09:00 by zxq9 · 0 comments
zxq9 commented 2020-02-18 22:52:01 +09:00 (Migrated from gitlab.com)
Copy Link

Created by: hanssv

New features are only added to FATE compiler back-end - this asymmetry makes it hard to maintain the tests etc. From Iris on-wards the chain will only accept new FATE contracts so we should deprecate AEVM.

*Created by: hanssv* New features are only added to FATE compiler back-end - this asymmetry makes it hard to maintain the tests etc. From Iris on-wards the chain will only accept new FATE contracts so we should deprecate AEVM.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
WIP
bug
consensus-breaking
dependencies
documentation
duplicate
effort: high
effort: low
effort: medium
effort: trivial
enhancement
good first issue
help wanted
invalid
maintenance
question
task/feature
todo-in-rewrite
wontfix
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
pig lipstick
Muggle-facing enhancements
question
More information is needed
wontfix
This won't be fixed
No Label
effort: low
maintenance
Milestone
No items
No Milestone iris
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QPQ-AG/sophia#226
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?