-
Notifications
You must be signed in to change notification settings - Fork 144
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
Implements apply_message and apply_implicit_message #353
Conversation
* Refactored return err messages
Co-Authored-By: Austin Abell <austinabell8@gmail.com>
) -> ( | ||
Serialized, | ||
DefaultRuntime<'_, 'm, '_, ST, DB, SYS>, | ||
Option<ActorError>, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't understand why this is an option? If internal_send is successful, we can return ExitCode::Ok, otherwise return actor_err, no?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems weird to construct an error upon a successful call. More preference I suppose.
Summary of changes
Changes introduced in this pull request:
apply_message
apply_implicit_message
send
to return a tuplesyscalls
to VM structI noticed in the spec they are applying a
network_tx_fee
tototal_cost
which is checked against thefrom_actors
balance to see if there are sufficient funds. I added a TODO for this, however, I am not sure what thatnetwork_tx_fee
is comprised of.Additionally, I added
apply_implicit_message
as it exists in the lotus implementation, but I do not seeapply_tipset_messages
in the implementation anymore. I did not remove it from our implementation as it seems that it will be required?Reference issue to close (if applicable)
Closes #340
Other information and links