-
Notifications
You must be signed in to change notification settings - Fork 0
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
Maybe just call it mscorlib? #3
Comments
It's part of a common set of nomenclature when dealing with ffi. The first crate is just straight ffi bindings, with a suffix, sys. The next layer up deals with and wraps the unsafe bits (raw pointers, conversions, etc,) and has a suffix of safe. Consider odbc-safe: https://crates.io/crates/odbc-safe |
The |
Sorry, this fell by the wayside with other stuff happening in my life. So I think the situation with odbc, odbc-safe, odbc-sys is that there are three layers and there needs to be some distinguishing. I wasn't sure how many layers I'd eventually need, so I went with the future-proofed path in case I did need 3. Does that make sense? |
Sure. It's just the one without any suffix is user/downstream-oriented. |
It is unusual to include the word "safe" in Rust, since anything unsafe in Rust is opt-in.
The text was updated successfully, but these errors were encountered: