leanprover-community / leanprover-community/repl
Fork safety
Open
Nobody has claimed this yet.
- Dominant language
- Lean
- Stars
- 228
- Forks
- 69
- Avg merge
- 15m
- Merged PRs (30d)
- 4
Description
Is REPL process / lean state - fork-safe?
E.g. is it possible to have a parent REPL process, do all imports there and then just fork this prepared process and then do verification inside the child processes?
Are there any bad global/non-threadlocal state in REPL/Lean?
Thanks!
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
Investigate whether a parent REPL process can import everything once, fork child processes, and perform verification safely. Check for global or non-thread-local state in the REPL and Lean, then document the conditions under which this workflow is safe or unsafe.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100