这是我的 C++11 项目中一些模板元黑客的 MCVE:
#include <functional>
struct Foo {};
template <typename... T>
void expect(std::function<void(const T&)>&&... onSuccess)
{
expect<T...>(
std::forward<std::function<void(const T&)>>(onSuccess)...,
0,
[](){}
);
}
template <typename... T>
void expect(
std::function<void(const T&)>&&... onSuccess,
const time_t timeout,
std::function<void()>&& onExpiry
)
{
// ...
}
int main()
{
expect<Foo>([=](const Foo&) {}, 42u, [=](){});
}
它在 GCC 6.1 (使用 Coliru)、GCC 4.8.5 和 GCC 4.8.2 x86_64 (使用GodBolt)中构建良好,但是当我将它插入我的开发环境时(在 CentOS 6 x86 上通过 devtoolset-2 是 GCC 4.8.2 ) 我得到错误:
[root@localhost ~]# g++ test.cpp -std=c++11 -o test
test.cpp: In function ‘int main()’:
test.cpp:27:47: error: no matching function for call to ‘expect(main()::__lambda1, unsigned int, main()::__lambda2)’
expect<Foo>([=](const Foo&) {}, 42u, [=](){});
^
test.cpp:27:47: note: candidates are:
test.cpp:6:6: note: template<class ... T> void expect(std::function<void(const T&)>&& ...)
void expect(std::function<void(const T&)>&&... onSuccess)
^
test.cpp:6:6: note: template argument deduction/substitution failed:
test.cpp:27:47: note: mismatched types ‘std::function<void(const T&)>’ and ‘unsigned int’
expect<Foo>([=](const Foo&) {}, 42u, [=](){});
^
test.cpp:16:6: note: template<class ... T> void expect(std::function<void(const T&)>&& ..., time_t, std::function<void()>&&)
void expect(
^
test.cpp:16:6: note: template argument deduction/substitution failed:
test.cpp:27:47: note: cannot convert ‘<lambda closure object>main()::__lambda1{}’ (type ‘main()::__lambda1’) to type ‘time_t {aka long int}’
expect<Foo>([=](const Foo&) {}, 42u, [=](){});
[root@localhost ~]# g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/opt/rh/devtoolset-2/root/usr/libexec/gcc/i686-redhat-linux/4.8.2/lto-wrapper
Target: i686-redhat-linux
Configured with: ../configure --prefix=/opt/rh/devtoolset-2/root/usr --mandir=/opt/rh/devtoolset-2/root/usr/share/man --infodir=/opt/rh/devtoolset-2/root/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,fortran,lto --enable-plugin --with-linker-hash-style=gnu --enable-initfini-array --disable-libgcj --with-isl=/builddir/build/BUILD/gcc-4.8.2-20140120/obj-i686-redhat-linux/isl-install --with-cloog=/builddir/build/BUILD/gcc-4.8.2-20140120/obj-i686-redhat-linux/cloog-install --with-mpc=/builddir/build/BUILD/gcc-4.8.2-20140120/obj-i686-redhat-linux/mpc-install --with-tune=generic --with-arch=i686 --build=i686-redhat-linux
Thread model: posix
gcc version 4.8.2 20140120 (Red Hat 4.8.2-15) (GCC)
我可以通过在第二个重载onSuccess
之后timeout
和onExpiry
第二个重载中解决这个问题,但我认为原始排序更容易让开发人员使用,如果可以的话,我宁愿保留它。
那么还有其他方法吗?
而且,对于奖励积分,实际发生了什么?