IronLanguages / IronLanguages/ironpython3
Move DLR generator scripts to DLR repo
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 316
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 1
Description
We should consider moving the following generator scripts which seem to be for the DLR:
generate_casts, generate_comdispatch, generate_dynamic_instructions, generate_dynsites, generate_exception_factory, generate_reflected_calls, generate_tree, generate_tuples
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 locating the eight named generator scripts: generate_casts, generate_comdispatch, generate_dynamic_instructions, generate_dynsites, generate_exception_factory, generate_reflected_calls, generate_tree, and generate_tuples. Check their DLR ownership and dependencies, then verify that moving them to the DLR repository leaves IronPython's generation workflow intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, python
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100