-
Notifications
You must be signed in to change notification settings - Fork 2k
Feat: Solidity Repl #230
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
Comments
Omg would be so dope if it had all your contract abis loaded to go so you could do something like |
some thoughts after skimming solidity-shell's codebase it appears an appropriate approach to this could be:
There's also If anyone would like to take this on, I'm happy to help |
Can we persist variables? That’d be a dream |
totally, what I'm thinking is something like this: pub struct SolRepl {
/// this gives us the user input
rl: Readline,
/// this stores all previously evaluated user inputs, like vars, etc
session: Session,
/// the type that executes all the things
sol: Sol,
}
struct Sol {
/// the virtual project where we store all the things (perhaps not even necessary if we only use solc standard json input/output)
project: TempProject,
// stores all the deployed contracts/abis etc...
state: SolState
} then the actual repl would probably look something like: loop {
let input = self.rl.readline();
let res = self.sol.execute(&line);
println!("{}", res);
} |
Would love to see gas cost printed after evaluation :) |
closed via #3465 |
Have seen a few requests for a solidity repl. This can be a tracking issue for the feature
Helpful things:
The text was updated successfully, but these errors were encountered: