You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on the cross contract call, I ran into a problem with import engine types to interact with Aurora contract.
It should be possible to import the input and output types from other libs without importing the engine crate, so those types could be moved to engine-types.
The text was updated successfully, but these errors were encountered:
@karim-en If you look closely at the code, you can see in some places there is a very strong interweaving with engine crate. This means that these parameters cannot simply be taken and transferred. Therefore, it will be great if you give specific suggestions.
@mrLSD hm, at least we can move part of them and then think about types with hard links. For example I was already able to move the SubmitResult to temporarily lib.
Definitely the copy past will not works, so some refactoring should be done.
While working on the cross contract call, I ran into a problem with import engine types to interact with Aurora contract.
It should be possible to import the input and output types from other libs without importing the engine crate, so those types could be moved to
engine-types
.The text was updated successfully, but these errors were encountered: