-
Notifications
You must be signed in to change notification settings - Fork 17
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
⚡️ Faster contract execution in genesis by not running in r0vm #618
Conversation
.try_into() | ||
.expect("Failed to decode state"); | ||
|
||
let _ = stdout.write_str("Init token contract"); |
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.
why not use env::log ?
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.
this function doesn't seem to match the guest 🤔
0a4e9ab
to
cc48de3
Compare
3d7d06a
to
0b857ca
Compare
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.
On en a parlé à l'oral; on utilise le statedigest des contrats comme était directement le state. Ça fait l'objet d'une autre pr pour l'adapter
@@ -175,6 +179,32 @@ impl TryFrom<sdk::StateDigest> for HyllarToken { | |||
} | |||
} | |||
|
|||
pub fn execute(stdout: &mut impl std::fmt::Write, contract_input: ContractInput) -> HyleOutput { |
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.
pourquoi pas mettre cette fonction directement dans HyllarPseudoExecutor (qu'on renommerait alors HyllarExecutor) ?
|
||
#[derive(Default)] | ||
pub struct TxExecutor<S: StateUpdater> { | ||
full_states: S, |
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.
Je trouve le nom un peu ambiguë
J"aurais appelé ça all_states
, ou qulque chose qui laisse ententre que c'est le state de chaque contract dans la Tx
Le mot full donne l'impression que c'est poru dire 'state complet' imo
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.
On vient d'en parler à l'oral :
Le typage des variables est confusing; il faut faire la distinction State (: Digestable) et StateDigest (et adapter les noms de variables en conséquence :p
0b857ca
to
adcf973
Compare
No description provided.