Skip to content

fix: handle constructor from reference to array #923

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

mizvekov
Copy link
Contributor

@mizvekov mizvekov commented Jul 8, 2025

isCopyOrMoveConstructorOrAssignment currently doesn't handle a constructor from a reference to array. I am not sure why this is not seen on CI, but it is reproducible from llvm 20.1.7, as available in macos homebrew.

@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://923.mrdocs.prtest2.cppalliance.org/index.html

isCopyOrMoveConstructorOrAssignment currently doesn't handle a constructor
from a reference to array. I am not sure why this is not seen on CI,
but it is reproducible from llvm 20.1.7, as available in macos homebrew.
@alandefreitas alandefreitas force-pushed the fix-constructor-from-array branch from a4c5ad0 to 9f3b8bf Compare July 10, 2025 03:14
@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://923.mrdocs.prtest2.cppalliance.org/index.html

MRDOCS_CHECK_OR(paramRefPointeeNamed.Name, false);
auto const& paramName = paramRefPointeeNamed.Name;
auto const* paramRefPointeeNamed = get<NamedTypeInfo const*>(paramRefPointee);
if (!paramRefPointeeNamed)
Copy link
Collaborator

Choose a reason for hiding this comment

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

For reference, this could be MRDOCS_CHECK_OR(paramRefPointeeNamed, false).

MRDOCS_CHECK is that pattern people use with std::expected (like ? in Rust), so that code based on error types doesn't become impossible to read.

@alandefreitas alandefreitas merged commit 31f7d46 into cppalliance:develop Jul 10, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants