Should guard-foreign-escape use `#:callback-exns?`?
Open
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 19
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Now that the #:callback-exns? option for _fun has been added (in https://github.com/racket/racket/commit/bf8741e727fdf1844c65677f9b81ff71e5a42f3d), maybe guard-foreign-escape should use it:
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with racket/draw's draw-lib/racket/draw/unsafe/callback.rkt, especially guard-foreign-escape, and compare its use of _fun with the #:callback-exns? option introduced in the linked Racket commit. Done means determining whether the option should replace the current handling and updating the callback implementation consistently if so.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100