Why are some signals being declared as static?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 235
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Hello, recently i was studying the source code.
why are some signals being declared as static? For example, in cbrReveiver, cbrReceivedThroughtput_ is declared as static while cbrRcvdPkt_ is not static?
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
Locate the cbrReceiver source and compare the declarations of cbrReceivedThroughtput_ and cbrRcvdPkt_. Read the surrounding signal definitions and their uses to determine why one is static; the issue is resolved when that distinction is documented or clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100