Justification for Compiler and Linker Features
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- documentation
Research direction
Read the Compiler and Linker Features section at cps-org.github.io/cps/features.html#linker-features and review the linked discussion for the motivating use cases. Done means documenting the motivation, linking the discussion from relevant wiki pages, or creating a follow-up enhancement issue with a pull request that temporarily removes the page.
Written by the indexing model from the issue text.
Description
Scope
I'd like to kick off a thread discussing the Compiler and Linker Features section of the specification, mostly because I'm not sure what to do with it.
I'd like to hear the motivating use cases for these features. There are other alternatives to approaching those outcomes, including not worrying about relevant use cases yet, and I'd like to make sure I understand why this approach was used.
Note that most modern build and packaging systems have some notion of "profiles" or "toolchain specifications" that sort of serve the same purpose. I was expecting the ecosystem would want to converge on some commonalities in those problems, but I was expecting we could circle back to that later, or perhaps even in a different specification.
Completion Criteria
Any of these should be fine:
- Developer documentation to clarify the motivation for the use cases, perhaps just linking to this discussion from wiki pages if nothing else
- A new enhancement issue to circle back on this later
- ...and a pull request to remove the Compiler and Linker Features page, at least temporarily
- Dominant language
- Python
- Stars
- 191
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from cps-org/cps
-
Spec: `c-runtime-vendor` field also should document the "musl" typical value and "bionic"Possibly taken @leha-bot claimed this 1 day ago. Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 40/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
jbacalso24/mimry#291 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 Under an hour Newbie friendliness 82/100
eli-alvarado/us-watchlist-alerts#14 ·
Maintainers usually reply within 1 day
-
from-review-extraction python severity:nit
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
LearningCircuit/local-deep-research#7462 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
cathrynlavery/diagram-design#441 ·
Maintainers usually reply within 2 days
-
[Cleanup] Include the public header in work_split.cppPossibly taken @blozano-tt claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tenstorrent/tt-metal#60850 ·
Maintainers usually reply within 1 day