milksad
/
rust-secp256k1-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity

Remove TODOs for ffi functions for setting secp256k1 callbacks 

We would not want to use these functions internally because we rely on
USE_EXTERNAL_DEFAULT_CALLBACKS to provide the callbacks at link time,
see f7a4a7ef57. Moreover, we would not
want to export the functions either.
This commit is contained in:
Tim Ruffing 2019-08-08 19:20:36 +02:00
parent a055c3fdc0
commit 255d1ddd60
1 changed files with 1 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
src/ffi.rs
View File

@ -159,13 +159,6 @@ extern "C" {
seed32: *const c_uchar) seed32: *const c_uchar)
-> c_int; -> c_int;
// TODO secp256k1_context_set_illegal_callback
// TODO secp256k1_context_set_error_callback
// (Actually, I don't really want these exposed; if either of these
// are ever triggered it indicates a bug in rust-secp256k1, since
// one goal is to use Rust's type system to eliminate all possible
// bad inputs.)
// Pubkeys // Pubkeys
pub fn secp256k1_ec_pubkey_parse(cx: *const Context, pk: *mut PublicKey, pub fn secp256k1_ec_pubkey_parse(cx: *const Context, pk: *mut PublicKey,
input: *const c_uchar, in_len: usize) input: *const c_uchar, in_len: usize)
@ -738,4 +731,4 @@ mod tests {
assert_eq!(orig.len(), unsafe {strlen(test.as_ptr())}); assert_eq!(orig.len(), unsafe {strlen(test.as_ptr())});
} }
} }