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

Add printing details about compilation process #59

Conversation

kkawula
Copy link

@kkawula kkawula commented Oct 15, 2024

Comment on lines +27 to +28
println!("Compiling Sierra to Casm using USC...");

Copy link
Author

Choose a reason for hiding this comment

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

Because using USC almost always involves calling it by other tools, I believe that using the word "USC" here is appropriate

Choose a reason for hiding this comment

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

I don't really think this is helpful 🤔
Maybe we should add information about what is compiled?
Right now this would just print the same text multiple times in snforge - for each contract file.
It could also add cargo-style message at the end to mark finished compiling (e.g. with time it took to compile the file).

@franciszekjob
Copy link

franciszekjob commented Oct 15, 2024

@kkawula Could you please provide before/after comparison here (as screenshot)?

@kkawula
Copy link
Author

kkawula commented Oct 17, 2024

We are moving this feature to snforge, because we are collecting USC output from stdout.

@kkawula kkawula closed this Oct 17, 2024
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