debug_warn! macro
Open
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
I had the idea of including a macro that issues compiler warnings to make it easier for library developers to tell the user what, for example, is not recommended.
assert! is more likely to issue errors, but adding such a warning might be useful.
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
Start by reading the proposal for a debug_warn! macro alongside the existing assert! macro concept. Clarify the desired warning behavior, compiler and macro boundaries, and user-facing semantics before implementation; done means an agreed design and corresponding RFC-level resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100