diff options
| author | Friedemann Kleint <Friedemann.Kleint@qt.io> | 2020-10-12 13:50:24 +0200 |
|---|---|---|
| committer | Friedemann Kleint <Friedemann.Kleint@qt.io> | 2020-10-13 13:02:26 +0200 |
| commit | 85451c40f23a7298b5f35744e8588307e124a751 (patch) | |
| tree | d507d772fa63c084d64ac1886caa91e23c4864f2 /build_scripts/main.py | |
| parent | 6e2eb6917620675b8bbcce53a31204a1ecfb2424 (diff) | |
shiboken2: Use an AbstractMetaType for "void"
Previously, nullptr for an AbstractMetaType meant "void", particularly
for function return types. The problem with this is that it
causes unexpected crashes when dealing with template types
like QFuture<void> due to one of the instantiations of the
AbstractMetaType being nullptr. Use an AbstractMetaType based
on the existing "void" type entry for this.
Task-number: PYSIDE-1202
Change-Id: Ib06035cc7903480fd509f7e927d9114c55d51b62
Reviewed-by: Cristian Maureira-Fredes <cristian.maureira-fredes@qt.io>
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Diffstat (limited to 'build_scripts/main.py')
0 files changed, 0 insertions, 0 deletions