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

Move code reference to message #705

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Move code reference to message #705

wants to merge 2 commits into from

Conversation

chfast
Copy link
Member

@chfast chfast commented Feb 29, 2024

No description provided.

@chfast chfast force-pushed the code_in_msg branch 3 times, most recently from c3499c2 to a1df1d1 Compare March 13, 2024 18:51
@chfast chfast marked this pull request as ready for review March 13, 2024 20:36
@chfast chfast requested review from gumb0 and axic March 13, 2024 20:36
Copy link

codecov bot commented Mar 13, 2024

Codecov Report

Attention: Patch coverage is 97.22222% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 93.50%. Comparing base (f89284f) to head (c818948).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #705   +/-   ##
=======================================
  Coverage   93.49%   93.50%           
=======================================
  Files          25       25           
  Lines        3861     3865    +4     
  Branches      396      396           
=======================================
+ Hits         3610     3614    +4     
  Misses        139      139           
  Partials      112      112           

@@ -745,13 +739,9 @@ class VM
/// but without providing the Host context and interface.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update comment above

) -> ::evmc_vm::ffi::evmc_result
{
use evmc_vm::EvmcVm;

// TODO: context is optional in case of the "precompiles" capability
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this removed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wasn't able to translate the check easily and also not sure if this check isn't to heavy to be included in the bindings (unless this helps Rust translation somehow).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe TODO is worth to leave? It seems to point to something that is not yet implemented in bindings, but might be useful.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the check for instance/msg null should be removed. This is the place it ensures it won't be null.

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

Successfully merging this pull request may close these issues.

3 participants