You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket tracks progress for all other tickets meant to reduce the number of calls to user code repeated sections of the spec text. These are/will be implemented as merely PROOFS OF CONCEPT at first. The original goal of this was to improve runtime performance and reduce user code calls. Now the goal is to make the code more DRY for decreased proposal size and file size of compiled code in implementations.
As of #2826, we are getting rid of user code calls, so let's change the focus of this to just DRY the spec algorithms. Once #2826 happens, these should all be editorial changes, so they are less urgent; we should get them incorporated before declaring the spec stable though.
ptomato
changed the title
Fewer Calls & Size Reductions: Tracking Ticket
Spec Text Size Reductions: Tracking Ticket
Apr 18, 2024
This ticket tracks progress for all other tickets meant to reduce
the number of calls to user coderepeated sections of the spec text. These are/will be implemented as merely PROOFS OF CONCEPT at first. The original goal of this was to improve runtime performance and reduce user code calls. Now the goal is to make the code more DRY for decreased proposal size and file size of compiled code in implementations.Bugs
Tickets that BOTH require bugfixing AND will decrease # of user calls and reduce filesize when fixed:
Other DRY-ness
In addition to above, there are other ways to make the code more DRY:
maximumIncrements
/MAX_DIFFERENCE_INCREMENTS
The text was updated successfully, but these errors were encountered: