-
Notifications
You must be signed in to change notification settings - Fork 120
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 a paragraph about CTRL-C in Julia and GAP #3814
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3814 +/- ##
==========================================
- Coverage 81.28% 81.25% -0.03%
==========================================
Files 580 580
Lines 79352 79353 +1
==========================================
- Hits 64498 64481 -17
- Misses 14854 14872 +18 |
|
||
In a Julia session, one gets automatically back to the Julia prompt | ||
when an error occurs or when the user hits ctrl-C, | ||
and again some objects may be corrupted afterwards. |
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.
As I stated on Monday: this corruption issue in principle affects everything, including (AFAIK) code provided by the other cornerstones, and even native Julia code. So it feels odd to me to single out that it can happen when calling into GAP.
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.
The section is about differences between Julia and GAP, here the fact that GAP sessions have a break loop and Julia has not.
(cherry picked from commit a5df540)
No description provided.