Skip to content

Conversation

@jodavies
Copy link
Collaborator

Since the transform statements are sorting into the workspace, and might have to merge patches, make them use a par=1 EndSort. This commit makes this change for all transform statements, though only mularg is going to produce an explosion of terms here.

This fixes #230 and causes #183 to crash with a useful error (Term too complex during normalization).

@jodavies
Copy link
Collaborator Author

@vermaseren this one needs a sanity check, I am not 100% sure of the consequences of this change.

@vermaseren
Copy link
Collaborator

vermaseren commented May 10, 2024 via email

@coveralls
Copy link

coveralls commented May 10, 2024

Coverage Status

coverage: 48.748% (+0.04%) from 48.712%
when pulling 7831fd9 on jodavies:issue-230
into 0112aa6 on vermaseren:master.

Since the transform statements are sorting into the workspace,
and might have to merge patches, make them use a par=1 EndSort.
This commit makes this change for all transform statements, though
only mularg is going to produce an explosion of terms here.

This fixes form-dev#230 and causes form-dev#183 to crash with a useful error
(Term too complex during normalization).
@jodavies
Copy link
Collaborator Author

It is probably worth mentioning that mularg can be slow compared to repeated id statements (which are sorting the arguments each repeat).

@tueda
Copy link
Collaborator

tueda commented May 12, 2024

This is ready to merge, right?

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.

Crash in transform mulargs

4 participants