Open thedlop opened 2 years ago
That's a typo I made. There's probably other instances where it's wrong too. But it actually doesn't affect the runtime since the proper FFI functions are called with the args in the right spots. It's interesting that Swift can't catch the type error.
Of course a sweep should be made to correct these.
I figured Swift would complain about this but I guess a pointer is a pointer. Thanks for the clarification! I can keep posting instances of this here. I saw another in ErgoBoxCandidates
.
Var name should not be boxIdPtr
https://github.com/ergoplatform/sigma-rust/blob/develop/bindings/ergo-lib-ios/Sources/ErgoLib/Contract.swift#L39
Curious why a
DataInputPtr
is being used instead of anErgoBoxPtr
: https://github.com/ergoplatform/sigma-rust/blob/develop/bindings/ergo-lib-ios/Sources/ErgoLib/ErgoBox.swift#L514 when the C header has this as the method signature: