Pull harvest out into a separate pkg
- Dominant language
- Python
- Stars
- 328
- Forks
- 13
- Avg merge
- 49m
- Merged PRs (30d)
- 2
Description
Hi!
I’ve begun to use the harvest transform for a bunch of little things — for the purposes of this conversation, let’s say one of these things is a type of runtime debugger.
I started with a version of harvest which was a little more restrictive than the one in Oryx. But now I want to apply my debugger to more complicated programs, with control flow primitives.
now, this just about reaches the limit of what I would be comfortable maintaining separately (judging by the amount of touching internals)
Is there any talk of pulling harvest into JAX directly? (E.g. similar to experimental.checkify)?
Contributor guide
Research direction
Read Oryx's existing harvest transform and compare it with JAX's experimental.checkify, both mentioned in the issue. Clarify whether harvest should move into JAX and what package or API boundary is expected. Done requires a maintainer decision and an agreed migration scope, since the issue currently asks a design question rather than naming files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100