Why is 2htdp/planetcute so complicated?
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 112
- Forks
- 73
- Avg merge
- 9h 41m
- Merged PRs (30d)
- 1
Description
For whatever reason, 2htdp/planetcute exports everything as set! transformers. I'm honestly not sure why it does this in the first place, but furthermore, this doesn't play nice with require/typed in Typed Racket (trying to require these seems to trigger an infinite loop in TR).
This itself might be a bug in Typed Racket, but even so, the implementation of planetcute.rkt seems much too complicated for a relatively simple task. Why exactly is it implemented the way it is?
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 2htdp/planetcute and inspect how its exports use set! transformers. Reproduce the require/typed interaction in Typed Racket, then determine whether the infinite loop is in Typed Racket or planetcute; the issue is done when the cause and a concrete simplification or fix are established.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100