P2630: Kona (2022/11) feedback

Open
#306 1 comment 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
Stale
Tech stack
cpp
Domain
compilers

Research direction

Review the LEWG feedback recorded in this issue, including the discussion of tuple-like pairs, compile-time constant syntax, and convenience aliases. No source files or tests are named; completion would require determining how this feedback should be reflected in the relevant C++ proposal and confirming that the proposal addresses the committee observations.

Written by the indexing model from the issue text.

Description

LEWG voted that (begin, end) pairs don't need a special name; tuple-like is fine.

LEWG observed that syntax for compile-time constants was not ergonomic. Some suggested index_sequence<begin, end> (generalizing to index_sequence<IndexType, begin, end>). Some suggested convenience aliases, such as the following for a pair of compile-time int.

template<size_t X, size_t Y>
inline constexpr pair<integral_constant<int, X>, integral_constant<int, Y>> md_rng;
Dominant language
HTML
Stars
29
Forks
26
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 ORNL/cpp-proposals-pub

All issues in ORNL/cpp-proposals-pub

Similar issues

More Compilers issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.