avoid an attribute value after leaving a break loop #5731
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.
When one creates a f.p. group and triggers an element comparison then it may happen that GAP does not return.
Hit CTRL-C, then GAP enters a break loop,
and when one leaves it with
quit
then it is currently too late for triggering the computation of anIsomorphismPermGroup
or so that will control the behaviour of the group.Here is an example that shows the situation in GAP 4.12. The master branch version is already too clever for this particular group, currently I have no test example that demonstrate the changes there.
Does it make sense at all to try to avoid this kind of "object corruption" after leaving a break loop?