pybind/pybind11
1
0
Fork 0
mirror of https://github.com/pybind/pybind11.git synced 2026-05-11 17:00:34 +00:00
Code Issues Packages Projects Releases Wiki Activity

Resolve ambiguous factory spec. with nvcc+GCC (#6011)

Browse Source 
Explicitly specify the 4th template parameter in the
single-factory partial specialization of `factory` to
disambiguate it from the dual-factory specialization
when compiled with nvcc + GCC 14. Fixes #5565.

Co-authored-by: Oz <oz-agent@warp.dev>
This commit is contained in:
Marco Garten
2026-03-23 21:25:38 -07:00
committed by GitHub
parent dd95d53f0a
commit 2d1723c0d6
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
include/pybind11/detail/init.h
View File

@@ -367,8 +367,15 @@ template <typename CFunc,
struct factory;
// Specialization for py::init(Func)
// Note: The 4th template parameter `void_type()` is explicitly specified to resolve a
// template ambiguity with the dual-factory specialization below when compiled with
// nvcc + GCC (see #5565). Without it, both specializations match equally well for the
// single-factory case, since the 4th parameter defaults to
// `function_signature_t<void_type(*)()>` = `void_type()`, which the dual-factory
// specialization can also decompose as `AReturn(AArgs...)` with `AReturn=void_type`
// and `AArgs={}`.
template <typename Func, typename Return, typename... Args>
struct factory<Func, void_type (*)(), Return(Args...)> {
struct factory<Func, void_type (*)(), Return(Args...), void_type()> {
remove_reference_t<Func> class_factory;
// NOLINTNEXTLINE(google-explicit-constructor)