We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello, please see the following:
static_assert(std::is_same<decltype(make_span(std::declval<int[5]>())),span<const int>>::value, "make_span Broken"); static_assert(std::is_same<decltype(make_span(std::declval<int(&)[5]>())),span<int,5>>::value, "make_span Broken"); static_assert(std::is_same<decltype(make_span(std::declval<const int[5]>())),span<const int,5>>::value, "make_span Broken"); static_assert(std::is_same<decltype(make_span(std::declval<const int(&)[5]>())),span<const int,5>>::value, "make_span Broken");
The first case returns a span with dynamic extent, while the other 3 return a span with a fixed size extent.
While non-const rvalue reference to C arrays almost never appear anywhere, this is a minor inconsistency and looks like a bug?
The text was updated successfully, but these errors were encountered:
Above code in Compiler explorer.
Sorry, something went wrong.
No branches or pull requests
Hello, please see the following:
The first case returns a span with dynamic extent, while the other 3 return a span with a fixed size extent.
While non-const rvalue reference to C arrays almost never appear anywhere, this is a minor inconsistency and looks like a bug?
The text was updated successfully, but these errors were encountered: