Add dune facilities in the toplevel
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
Dune specific facilities like dune-build-info, virtual libraries, ... requires specific handling during linking. Dune could provide improved #require facilities in the toplevel using dune-plugin-site (work outside a dune workspace, less scanning, but only use META) or dune-rpc (can give access to local libraries, could use dune-package information).
Such feature should be added step by step, first redo the current #require feature, then ... but at the end the long run would be:
#require-privateto access private library of the current workspace- Possibility to build the library not yet built
- Virtual libraries handling
- Dune build info
ocaml(utop) ordune ocaml(resp.dune utop) could be handled differently the first would only access installed information.
It would help for:
- dune-build-info: #5566
Contributor guide
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 by examining the existing #require facility in the toplevel and the alternatives named in the issue: dune-plugin-site and dune-rpc. The proposed first milestone is to redo the current #require behavior; later completion would require deciding how private libraries, unbuilt libraries, virtual libraries, and dune-build-info are handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100