scheme/r7rs
17
30
Fork 1
Code Issues 181 Pull requests 1 Wiki Activity

letrec-values and letrec*-values #203

New issue
Open
opened 2024-09-19 20:14:38 +00:00 by dpk · 0 comments
dpk commented 2024-09-19 20:14:38 +00:00
Owner
Copy link

I’ve been trying to hold off on filing Procedural Fascicle-related issues in expectation of an imminent release announcement for the Macrological Fascicle (I am literally only waiting for JAR to update the DNS records for the scheme-reports.org domain). But as I mentioned this on IRC …

Should we have letrec-values and letrec*-values? At the moment we have an implicit letrec*-values through a non-top-level define-values. letrec-values can be implemented in terms of this. So these are as close to being ‘portable’ as can be.

I’ve been trying to hold off on filing Procedural Fascicle-related issues in expectation of an imminent release announcement for the Macrological Fascicle (I am literally *only* waiting for JAR to update the DNS records for the scheme-reports.org domain). But as I mentioned this on IRC … Should we have `letrec-values` and `letrec*-values`? At the moment we have an implicit `letrec*-values` through a non-top-level `define-values`. `letrec-values` can be implemented in terms of this. So these are as close to being ‘portable’ as can be.
dpk added this to the Procedural Fascicle milestone 2024-09-19 20:14:38 +00:00
dpk added the
Foundations
 label 2024-09-19 20:14:38 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
pages
c-trichotomy
global-id-prop-ref
allow-van-tonder-like-expanders
No results found.
Labels
Clear labels   
Batteries

Issues for the Batteries volume of the report, providing a standard library

  
Cleanup

Issues where inconsistencies or other infelicities have arisen

  
Consent Docket

Items which will be automatically be given a certain resolution if no objection is made by a certain date

  
Environments

Issues for the Environments volume of the report, providing OS interfaces and similar

  
Foundations

Issues for the Foundations volume of the report, related to the core language semantics

  
Macrological Fascicle

   
Meta

Procedural and organisational issues

  
Multiple proposals exist

Multiple competing, concrete proposals to resolve this issue exist (whether they are SRFI or still only pre-SRFI)

  
Pie-in-the-sky ideas

Ideas currently lacking any form of worked-out proposal

  
Problems without solutions

Problems we *must* solve but haven’t worked out any solution for yet

  
Public Comment

   
Publications

Issues related to the practicalities of making the report available

  
Question

For information and clarification

  
R6RS Compatibility

Issue touches on questions of R6RS compatibility

  
Resolution in draft

A resolution (not necessarily final) is specified in the current draft of the relevant fascicle

  
Specification exists

Proposals for which a viable, but incomplete specification text exists

  
SRFI/RnRS spec exists

A SRFI for this proposal exists, or a solution from another RnRS

No labels
Batteries
Cleanup
Consent Docket
Environments
Foundations
Macrological Fascicle
Meta
Multiple proposals exist
Pie-in-the-sky ideas
Problems without solutions
Public Comment
Publications
Question
R6RS Compatibility
Resolution in draft
Specification exists
SRFI/RnRS spec exists
Milestone
Clear milestone
No items
No milestone
Procedural Fascicle
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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: scheme/r7rs#203
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?