Don't leak keyword memory if it's avoidable #72

Closed
opened 2025-07-03 19:38:50 +00:00 by scott · 1 comment
Owner

Don't leak keywords if it's at all possible. I believe this is mostly an io issue, with keywords coming in from the frontend. Search for all instances of .leak(), and mitigate these wherever it's possible.

Don't leak keywords if it's at all possible. I believe this is mostly an io issue, with keywords coming in from the frontend. Search for all instances of `.leak()`, and mitigate these wherever it's possible.
scott added this to the Expanded: CC2 milestone 2025-07-03 19:38:50 +00:00
scott added the
optimization
label 2025-07-03 19:38:50 +00:00
Author
Owner

Actually, done. I just used consts in io. That's the only place I was leaking from.

Actually, done. I just used consts in `io`. That's the only place I was leaking from.
scott closed this issue 2025-07-04 18:22:04 +00:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: twc/ludus#72
No description provided.