fix resolution of std::complex

compiler-research · Feb 11, 2025 · 1ae94a5 · 1ae94a5
1 parent e5bc22c
commit 1ae94a5
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/src/Executors.cxx b/src/Executors.cxx
@@ -545,7 +545,7 @@ CPPYY_IMPL_ARRAY_EXEC(ComplexL, std::complex<long>,      )
 PyObject* CPyCppyy::Complex##code##Executor::Execute(                        \
     Cppyy::TCppMethod_t method, Cppyy::TCppObject_t self, CallContext* ctxt) \
 {                                                                            \
-    static Cppyy::TCppType_t scopeid = Cppyy::GetComplexType(#type);         \
+    static Cppyy::TCppScope_t scopeid = Cppyy::GetScope("std::complex<"#type">");\
     std::complex<type>* result =                                             \
         (std::complex<type>*)GILCallO(method, self, ctxt, scopeid);          \
     if (!result) {                                                           \
@@ -567,7 +567,7 @@ PyObject* CPyCppyy::STLStringExecutor::Execute(
 // execute <method> with argument <self, ctxt>, construct python string return value
 
 // TODO: make use of GILLCallS (?!)
-    static Cppyy::TCppType_t sSTLStringScope = Cppyy::GetFullScope("std::string");
+    static Cppyy::TCppScope_t sSTLStringScope = Cppyy::GetFullScope("std::string");
     std::string* result = (std::string*)GILCallO(method, self, ctxt, sSTLStringScope);
     if (!result)
         result = new std::string{};