Use concepts to implement most functions more concisely
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- cpp
- Domain
- performance
Research direction
Start by locating the functions that use verbose template signatures like the shown permute overload, then review the existing xvec concepts listed in the issue. Done means the applicable functions use those concepts more concisely without changing their behavior, but the issue does not identify the files, tests, or complete scope.
Written by the indexing model from the issue text.
Description
Instead of:
template<typename _Tp, typename _Abi, std::unsigned_integral _Up, typename _AbiU>
constexpr simd<_Tp, basic_simd<_Up, _AbiU>::size()>
permute(const basic_simd<_Tp, _Abi>& v, const basic_simd<_Up, _AbiU>& indexes){ return simd_details::permute(vendor, v.to_builtin(), indexes.to_builtin()); }
do:
constexpr auto
permute(const simd_any auto& v, const simd_integral auto& indexes) {...}
Concepts available include the following, though these are an xvec feature not a standard feature.
simd_any
simd_integral
simd_signed_integral
simd_unsigned_integral
simd_float
simd_register (fits into a target register)
simd_multi_register
...
- Dominant language
- C++
- Stars
- 6
- Forks
- 2
- Avg merge
- 2d 47m
- Merged PRs (30d)
- 18
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from intel/xvec
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 40/100
Maintainers usually reply within 1 day
-
C++29 extension
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
C++29 extension
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
backlog
Difficulty 1/5 Under an hour Newbie friendliness 91/100
EchoTools/nevr-runtime#1108 ·
Maintainers usually reply within 1 day
-
Status: Needs confirmation Status: Needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
boykopovar/AnyPS5#12124 ·
Maintainers usually reply within 1 day
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day