big modules printed in error messages
Nobody has claimed this yet.
- Dominant language
- Macaulay2
- Stars
- 435
- Forks
- 297
- Avg merge
- 4d 20h
- Merged PRs (30d)
- 11
Description
@Devlin-Mallory and I frequently run into silly errors where something like ranks M for a huge module M will take a long time only to print an error that ranks is an undefined symbol. Perhaps the error printing routine shouldn't try to print the content of modules, sheaves, complexes, etc?
Perhaps there should be a new method like errorPrint which can be used to determine how to print an object in the error.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the error-printing routine responsible for displaying objects in errors, then inspect how modules, sheaves, and complexes are rendered. Done should mean errors such as an undefined symbol do not spend excessive time printing the contents of very large objects while still providing useful error output.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100