and and or should be short-circuiting special forms #67

Open
opened 2024-06-05 17:18:18 +00:00 by scott · 0 comments
Owner

That way, you can bail out before a form would panic, or an expensive computation would happen.

This will entail making and and or reserved words in the scanner, adding dedicated parsing, and specific interpreting functions. I don't think it has validation consequences. (Using a placeholder will be a parse error.) Should be straightforward.

That way, you can bail out before a form would panic, or an expensive computation would happen. This will entail making `and` and `or` reserved words in the scanner, adding dedicated parsing, and specific interpreting functions. I don't think it has validation consequences. (Using a placeholder will be a parse error.) Should be straightforward.
scott added this to the 0.2.0 milestone 2024-06-05 17:18:20 +00:00
scott added the
next
semantics
optimization
labels 2024-06-05 17:18:35 +00:00
scott added this to the Better errors project 2024-07-21 17:44:48 +00:00
scott modified the project from Better errors to Completing the language 2024-07-21 20:16:34 +00:00
Sign in to join this conversation.
No Milestone
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#67
No description provided.