-
Notifications
You must be signed in to change notification settings - Fork 20
Use the C _Complex number type #72
Copy link
Copy link
Open
Labels
analysis-lowAnalysis on this issue is low importance, or it is out of scope for nowAnalysis on this issue is low importance, or it is out of scope for nowl-rustChanges that are mainly in RustChanges that are mainly in Rustneeds-rustNeeds rust compiler or tooling changesNeeds rust compiler or tooling changesp-semanticsLanguage semantics differencesLanguage semantics differencessolved-rustcSolved by the Rust compilerSolved by the Rust compilert-use-caseA Rust/C++ interop usage exampleA Rust/C++ interop usage example
Description
Activity
Metadata
Metadata
Assignees
Labels
analysis-lowAnalysis on this issue is low importance, or it is out of scope for nowAnalysis on this issue is low importance, or it is out of scope for nowl-rustChanges that are mainly in RustChanges that are mainly in Rustneeds-rustNeeds rust compiler or tooling changesNeeds rust compiler or tooling changesp-semanticsLanguage semantics differencesLanguage semantics differencessolved-rustcSolved by the Rust compilerSolved by the Rust compilert-use-caseA Rust/C++ interop usage exampleA Rust/C++ interop usage example
Using C's _Complex (complex number) type is tricky because the function call ABI differs between compilers. This means only the Rust compiler can fix this interop issue.
The Rust compiler is adding support in rust-lang/rust#158885