Good-enough error reporting #70

Closed
opened 2024-06-06 03:07:05 +00:00 by scott · 3 comments
Owner

Good-enough version of #36 for computer class.

Developing this as part of my work on #62, giving myself better error messages for prelude debugging.

Good-enough version of #36 for computer class. Developing this as part of my work on #62, giving myself better error messages for prelude debugging.
Author
Owner

Develop an actual checklist for this.

Develop an actual checklist for this.
Author
Owner

Still WIP, but much closer with e428fccc86

Still WIP, but much closer with https://alea.ludus.dev/twc/ludus/commit/e428fccc86d4ee4f9fc56d082558b36338b6213e
scott added this to the Computer Class milestone 2024-06-14 19:34:39 +00:00
Author
Owner

We got good enough error reporting for computer class! They're still not great; parsing errors are a mess of off-by-one. But definitely they did what the needed to.

We got good enough error reporting for computer class! They're still not great; parsing errors are a mess of off-by-one. But definitely they did what the needed to.
scott closed this issue 2024-06-21 14:37:43 +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#70
No description provided.