racket/unsafe/undefined should not be allowed #1

Open
opened 2018-06-03 00:12:43 +01:00 by SuzanneSoy · 0 comments
SuzanneSoy commented 2018-06-03 00:12:43 +01:00 (Migrated from github.com)

If racket/unsafe/undefined can actually be used for unsoundness, it should not be allowed. Instead, we should use an ad-hoc implementation of optional arguments (have a standard wrapper function with optional arguments using a unique symbol to indicate their absence, and pass those values to the "barrier" which verifies purity, so that # is never used.

If racket/unsafe/undefined can actually be used for unsoundness, it should not be allowed. Instead, we should use an ad-hoc implementation of optional arguments (have a standard wrapper function with optional arguments using a unique symbol to indicate their absence, and pass those values to the "barrier" which verifies purity, so that #<unsafe-undefined> is never used.
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: suzanne.soy/delay-pure#1
No description provided.