Skip to content

Eliminate single element tuple-like from user-facing API#42

Open
yaito3014 wants to merge 24 commits intomainfrom
eliminate-one-size-tuple
Open

Eliminate single element tuple-like from user-facing API#42
yaito3014 wants to merge 24 commits intomainfrom
eliminate-one-size-tuple

Conversation

@yaito3014
Copy link
Member

@yaito3014 yaito3014 commented Feb 18, 2026

fixes #18

Todo

@yaito3014 yaito3014 self-assigned this Feb 18, 2026
@yaito3014 yaito3014 added the enhancement New feature or request label Feb 18, 2026
@yaito3014 yaito3014 force-pushed the eliminate-one-size-tuple branch from a4ace3a to b0533fb Compare February 18, 2026 20:29
@cppwarningnotifier
Copy link

EnvironmentC++23C++26
x4Clang21Debug✅success✅success
Release✅success✅success
GCC14Debug✅success✅success
Release✅success✅success
MSVC2022Debug✅success✅success
Release✅success✅success
2026Debug✅success✅success
Release✅success✅success

@saki7 saki7 added the tests needed Unit tests are required for all public API label Feb 18, 2026
@saki7

This comment was marked as resolved.

@saki7 saki7 changed the title Eliminate size one tuple from user-facing API Eliminate single element tuple-like from user-facing API Feb 19, 2026
@saki7

This comment was marked as resolved.

@yaito3014 yaito3014 force-pushed the eliminate-one-size-tuple branch from c475655 to 0e62b8a Compare February 19, 2026 21:12
template<traits::NonUnusedAttr Source, traits::CategorizedAttr<traits::variant_attr> Dest>
requires (!traits::is_size_one_sequence_v<Source>)
requires
// traits::variant_has_substitute_v<Dest, Source> && // TODO: investigate compilation error due to existance of this constraint
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request tests needed Unit tests are required for all public API

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Single element tuple-like needs to be eliminated from user-facing API

2 participants