Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option of string not ffi safe #67

Open
ZakharEl opened this issue Apr 12, 2024 · 3 comments
Open

Option of string not ffi safe #67

ZakharEl opened this issue Apr 12, 2024 · 3 comments

Comments

@ZakharEl
Copy link

I have a trait that has a method that returns a stabby::option::Optionstabby::string::String. It says that it resturns the type stabby::stabby_abi::End, which is not FFI-safe.

@ZakharEl
Copy link
Author

Ah it only gives me trouble with methods returning stabby::option::Option<stabby::string::String> if I use stabby::option::Option::None() in the method body.

@ZakharEl
Copy link
Author

if used in stable trait default method body it will not compile but if the method default is left undefined and then the method is implemented for a type using stabby::option::Option::None() in its body it will compile with same messages as a warning instead of an error.

@xuchaoqian
Copy link

I have a trait that has a method that returns a stabby::option::Optionstabby::string::String. It says that it resturns the type stabby::stabby_abi::End, which is not FFI-safe.

Met the similar case. It should be a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants