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

Handle generic results #11

Open
SAtacker opened this issue Sep 1, 2024 · 6 comments
Open

Handle generic results #11

SAtacker opened this issue Sep 1, 2024 · 6 comments

Comments

@SAtacker
Copy link
Contributor

SAtacker commented Sep 1, 2024

Currently we return -1 or some weird old C way of doing things and is non-standard. This is vague and unclear for any user. It is also unclear how we handle exceptions.

@pingu-73
Copy link
Contributor

pingu-73 commented Sep 1, 2024

@SAtacker do you have any suggestion for what to do instead of returning -1
also for the exceptions handling are you referring to cpp side or rust side

@SAtacker
Copy link
Contributor Author

SAtacker commented Sep 1, 2024

Does Rust std:: use something like returning None type? Can we do something like that?

@pingu-73
Copy link
Contributor

pingu-73 commented Sep 1, 2024

Does Rust std:: use something like returning None type? Can we do something like that?

Option type in rust has None

@SAtacker
Copy link
Contributor Author

SAtacker commented Sep 1, 2024

Does Rust std:: use something like returning None type? Can we do something like that?

Option has None

Let's use it then, thanks!

@pingu-73
Copy link
Contributor

pingu-73 commented Sep 1, 2024

Sure, I'll work on it

@SAtacker
Copy link
Contributor Author

SAtacker commented Sep 1, 2024

Sure, I'll work on it

Thanks!

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