Introduce AENSv2 namespace to introduce raw data pointers #917
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "add_aens_data_pointer"
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?
Created by: hanssv
This PR is supported by the Æternity Crypto Foundation
approved this merge request
Created by: radrow
I don't like mixing incompatible functionalities in the same namespace. Let's create
AENS2
namespace and pack all the new stuff in there.Created by: radrow
Btw, shouldn't there be changes in
aeso_fcode_to_fate
?Created by: hanssv
I really like the idea of a whole new top-level namespace, I'll test it and see how it turns out.
@radrow there are no changes at the byte code instruction level (yet!) so no changes necessary in
aeso_fcode_to_fate
Created by: hanssv
Moved all the active stuff + the new data pointer to
AENSv2
- this turned out nicely I think - good call @radrow !Created by: radrow
Review: Approved
Looks way better
Merged by: hanssv at 2022-11-16 20:31:44 UTC