`call-in-continuation` and immediate continuation marks
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- backend
Research direction
Start by reading the continuation mark implementation and its tests; the issue does not name specific files or test cases. Reproduce the final expression and compare its result with the preceding examples. Done means the immediate continuation mark lookup inside the thunk passed to call-in-continuation returns tail.
Written by the indexing model from the issue text.
Description
Consider the following expression:
(call/cc
(lambda (k1)
(call-in-continuation k1
(lambda ()
(call/cc
(lambda (k2)
(eqv? k1 k2)))))))
It evaluates to #t, which reflects the fact that the last expression of the thunk argument to call-in-continuation is evaluated in the continuation of the whole expression.
This, however, is not reflected by the implementation of immediate continuation marks. Consider:
(with-continuation-mark 'key 'tail
(call/cc
(lambda (k1)
(call-with-immediate-continuation-mark 'key values))))
This expression evaluates to tail, which reflects the fact that key is part of the immediate table of marks of the continuation of the whole expression.
Now consider:
(with-continuation-mark 'key 'tail
(call/cc
(lambda (k1)
(call-in-continuation k1
(lambda ()
(call-with-immediate-continuation-mark 'key values))))))
In the current implementation of continuation marks, this evaluates to #f. In other words, the implementation of call-with-immediate-continuation-mark fails to deliver the immediate marks of the continuation to the call of the thunk argument to call-in-continuation.
- Dominant language
- Scheme
- Stars
- 7.4k
- Forks
- 1k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 19
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cisco/ChezScheme
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cisco/ChezScheme#1110 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
cisco/ChezScheme#1111 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 12/100
cisco/ChezScheme#1101 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cisco/ChezScheme#1078 · 1 comment ·
Maintainers usually reply within 1 day
-
RFC: solution to clangd not finding "scheme.h"Possibly taken @reginaldalfret claimed this 20 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
cisco/ChezScheme#1073 · 1 comment ·
Maintainers usually reply within 1 day
All issues in cisco/ChezScheme
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kludex/python-multipart#375 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Termix-SSH/Plugin-Hosts-Config#14 · 1 comment ·
Maintainers usually reply within 4 days
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
quantum-php/framework#692 ·
Maintainers usually reply within 1 day
-
area:web kind:bug priority:p2 ready
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 11 days