ORNL / ORNL/cpp-proposals-pub

P0009: Same interface for `is_always_strided`

Open
#182 2 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

The mapping for layout_stride has a strides() member function to retrieve at once all the strides whereas layout_left and layout_right do not. I was wondering if it could be possible to require for all mappings satisfying is_always_strided() to implement both stride(size_t) and strides() ? This could ease writing generic code with a strided_layout concept.

Thomas P.

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

Review the proposed layout_stride, layout_left, and layout_right mapping interfaces and the is_always_strided() requirement described in the issue. Determine whether requiring both stride(size_t) and strides() is appropriate for a generic strided_layout concept; done means the proposal has a settled direction and the interface requirements are clearly documented.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.