为什么 std::forward 放弃 constexpr-ness?
由于未声明 constexpr
,std::forward
将放弃将参数转发到的任何函数的 constexpr 性。 为什么 std::forward
没有声明 constexpr
本身,以便它可以保留 constexpr-ness?
示例:(使用 g++ snapshot-2011-02 进行测试-19)
#include <utility>
template <typename T> constexpr int f(T x) { return -13;}
template <typename T> constexpr int g(T&& x) { return f(std::forward<T>(x));}
int main() {
constexpr int j = f(3.5f);
// next line does not compile:
// error: ‘constexpr int g(T&&) [with T = float]’ is not a constexpr function
constexpr int j2 = g(3.5f);
}
注意:从技术上讲,很容易使 std::forward
constexpr,例如,像这样(注意在 g 中 std::forward
已被替换为fix::forward
):
#include <utility>
namespace fix {
/// constexpr variant of forward, adapted from <utility>:
template<typename Tp>
inline constexpr Tp&&
forward(typename std::remove_reference<Tp>::type& t)
{ return static_cast<Tp&&>(t); }
template<typename Tp>
inline constexpr Tp&&
forward(typename std::remove_reference<Tp>::type&& t)
{
static_assert(!std::is_lvalue_reference<Tp>::value, "template argument"
" substituting Tp is an lvalue reference type");
return static_cast<Tp&&>(t);
}
} // namespace fix
template <typename T> constexpr int f(T x) { return -13;}
template <typename T> constexpr int g(T&& x) { return f(fix::forward<T>(x));}
int main() {
constexpr int j = f(3.5f);
// now compiles fine:
constexpr int j2 = g(3.5f);
}
我的问题是:为什么 std::forward
不像 fix::forward
那样定义?
注意2:这个问题与我的另一个关于 constexpr std 的问题有些相关::tuple as std::forward
不是 constexpr
是无法通过调用创建 std::tuple
的技术原因它的 cstr 带有右值,但这里的问题显然(更)更普遍。
Being not declared constexpr
, std::forward
will discard constexpr-ness for any function it forwards arguments to. Why is std::forward
not declared constexpr
itself so it can preserve constexpr-ness?
Example: (tested with g++ snapshot-2011-02-19)
#include <utility>
template <typename T> constexpr int f(T x) { return -13;}
template <typename T> constexpr int g(T&& x) { return f(std::forward<T>(x));}
int main() {
constexpr int j = f(3.5f);
// next line does not compile:
// error: ‘constexpr int g(T&&) [with T = float]’ is not a constexpr function
constexpr int j2 = g(3.5f);
}
Note: technically, it would be easy to make std::forward
constexpr, e.g., like so (note that in g std::forward
has been replaced by fix::forward
):
#include <utility>
namespace fix {
/// constexpr variant of forward, adapted from <utility>:
template<typename Tp>
inline constexpr Tp&&
forward(typename std::remove_reference<Tp>::type& t)
{ return static_cast<Tp&&>(t); }
template<typename Tp>
inline constexpr Tp&&
forward(typename std::remove_reference<Tp>::type&& t)
{
static_assert(!std::is_lvalue_reference<Tp>::value, "template argument"
" substituting Tp is an lvalue reference type");
return static_cast<Tp&&>(t);
}
} // namespace fix
template <typename T> constexpr int f(T x) { return -13;}
template <typename T> constexpr int g(T&& x) { return f(fix::forward<T>(x));}
int main() {
constexpr int j = f(3.5f);
// now compiles fine:
constexpr int j2 = g(3.5f);
}
My question is: why is std::forward
not defined like fix::forward
?
Note2: this question is somewhat related to my other question about constexpr std::tuple as std::forward
not being constexpr
is the technical reason why std::tuple
cannot be created by calling its cstr with rvalues, but this question here obviously is (much) more general.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
一般的答案是,C++ 委员会的库工作组尚未对工作草案进行详尽的搜索,寻找使用新核心设施的机会。这些功能已被用于人们有时间和意愿去研究可能的用途,但没有时间进行详尽检查的地方。
有一些关于作品中 constexpr 的其他用途的论文,例如 2010 年 11 月邮寄。
The general answer is that the C++ committee's Library Working Group have not done an exhaustive trawl through the working draft looking for opportunities to use the new core facilities. These features have been used where people have had the time and inclination to look at possible uses, but there is not the time for exhaustive checking.
There are some papers regarding additional uses of
constexpr
in the works, such as those in the November 2010 mailing.