LayoutMapping requirements should constrain `is_always_*()` to be `constexpr`
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 29
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
This is because the primary use case is for constraining algorithms. For instance, the following should be prohibited:
extern bool foo;
struct _my_mapping {
/* ... */
static bool is_always_contiguous() { return foo; }
};
I think the way we should do this is to say in the table that the expression that needs to be valid is std::bool_constant<M::is_always_contiguous()>{}
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 LayoutMapping requirements table in the proposal text and read the surrounding requirements for the is_always_*() functions. Check how the table currently expresses validity, then update it so the proposed std::bool_constant<M::is_always_contiguous()>{} expression is the stated constraint and verify the wording consistently covers the relevant functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100