ORNL / ORNL/cpp-proposals-pub

P0009: What are the requirements on "reference" in accessor policy?

Open
#75 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
29
Forks
26
PR merge metrics
No merged PRs in 30d

Description

@crtrott @dsunder @dhollman

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

The issue body names no files, tests, or entry points; start by reading the P0009 proposal and the nine existing comments to determine the unresolved requirements for “reference” in accessor policy. Done means reaching and documenting a clear requirement, but the payload provides no concrete implementation or test location.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.