Conversation
ghost
commented
Jul 16, 2024
ghost
commented
Jul 16, 2024
alexrp
reviewed
Jul 31, 2024
Member
|
Thank you but I don't want to catch SIGINT. I think it is annoying as a user when processes do this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #20266
Closes #13045
When doing things that involve printing something to the terminal and then clearing it or having any kind of state in form of content printed to the terminal, it's very useful if you can handle the case of interruption. Even the standard library finds a use case for this:
std.Progress.Before:
After:
Ctrl+C is the most common way to abort the compiler while it is running.
Aborting it because of not needing it to run anymore is common, so why not handle this case if we can and keep output clean?