Should we reject an interface with private or protected functions?

Open
#451 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp
Domain
compilers

Research direction

The issue body names no files, tests, or entry points. First clarify whether private and protected interface functions should be rejected, and inspect the interface validation and reflection handling to identify the affected behavior. Done means an agreed policy is implemented and covered by tests for both access levels.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
C++
Stars
11
Forks
4
Avg merge
15h 44m
Merged PRs (30d)
145

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jbcoe/cc-protocol

All issues in jbcoe/cc-protocol

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.