gpu-gates: required-features 뒤의 죽은 stub main 정리
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 80/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- rust
- Domain
- build-system
Research direction
Start with the [[bin]] entries and required-features in crates/gpu-gates/Cargo.toml, then open each file in crates/gpu-gates/src/bin/*.rs and find the #[cfg(not(feature = ...))] fn main() stubs that the declared feature makes unreachable. Remove only those stubs, leaving the gated main intact. Done means just mac-static and bash tools/check-recipes.sh pass; the ptx-scan comparison is left to a maintainer.
Written by the indexing model from the issue text.
Description
required-features를 선언한 bin은 그 feature 없이 빌드될 수 없어서 #[cfg(not(feature))] fn main() stub이 죽은 코드입니다. bin마다 [[bin]] 선언을 확인하고 지워 주세요(기계적 작업).
- 파일:
crates/gpu-gates/src/bin/*.rs,crates/gpu-gates/Cargo.toml - 검증:
just mac-static,bash tools/check-recipes.sh. ptx-scan 비교는 메인테이너가 합니다.
자세한 내용: https://github.com/midagedev/bloomery/blob/main/docs/contrib/good-first-issues.md#L91
처음이시면 CONTRIBUTING.ko.md부터 봐 주세요. 작업을 맡으실 분은 댓글로 알려 주세요.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 4
- Avg merge
- 2h 53m
- Merged PRs (30d)
- 614
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from midagedev/bloomery
-
good first issue hardware help wanted no-box serve
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
good first issue hardware help wanted no-box
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 10/100
midagedev/bloomery#900 · 1 comment ·
Maintainers usually reply within 1 day
-
hardware help wanted model no-box
Difficulty 4/5 3-5 days Newbie friendliness 55/100
midagedev/bloomery#869 · 2 comments ·
Maintainers usually reply within 1 day
-
hardware help wanted measure no-box
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in midagedev/bloomery
Similar issues
-
desktop documentation
Difficulty 1/5 Under an hour Newbie friendliness 90/100
vfarcic/dot-agent-deck#2008 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 85/100
pbakaus/impeccable#1210 ·
Maintainers usually reply within 1 day
-
area: ci priority: P4 ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
shep-pm/shep#1249 · 1 comment ·
Maintainers usually reply within 1 day
-
L: javascript
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dependabot/dependabot-core#16744 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nautechsystems/nautilus_trader#5486 · 1 comment ·
Maintainers usually reply within 1 day