diff options
| author | Ville Voutilainen <ville.voutilainen@qt.io> | 2024-08-18 01:59:29 +0300 |
|---|---|---|
| committer | Ville Voutilainen <ville.voutilainen@qt.io> | 2024-08-18 21:46:30 +0000 |
| commit | 236c6ec6f4c777d0534539f1c293cfc74006a6eb (patch) | |
| tree | ed9fd165f88163c92a0e2a3f2325dfff304d2c28 /src/corelib/thread/qfutureinterface.cpp | |
| parent | 753d035e152f0572ba99717d04116a882a506bef (diff) | |
Fix an evaluated use of std::declval in qjnitypes.h
While other compilers don't seem to have trouble with this, the latest
NDK (27) compiler does. That compiler diagnoses the empty-pack case, even though in that case there is no actual use of declval, as the pack-expanded expression contains no use of declval.
For other compilers, that may work for functions that have no arguments, but will not work for any function that does have arguments; in that case, the attempt to use declval will always be ill-formed, and there will be an attempt to use declval.
The fix is straightforward; we have a Ret(*)(Args...), its return type
is simply Ret. So use a simple trait instead of the result of a call.
Task-number: QTBUG-127468
Change-Id: I0dc9e1201914ab94acc2940870be7c6d8cb16c12
Pick-to: 6.8 6.7
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Diffstat (limited to 'src/corelib/thread/qfutureinterface.cpp')
0 files changed, 0 insertions, 0 deletions
