@omershlo Here in this draft PR is only WASM specific diff to dev/vhnat/secp256-clean that is PR #6
You can run tests in wasm in chrome using wasm-pack with wasm-pack test --chrome --release. Adding --node argument will runt tests and/or on node.
Test test_serdes_bad_pk is ignored for now on wasm. Unfortunately #[wasm_bindgen(catch)] doesn't work as expected. More details here I rewrote one test test_wrong_homo_elgamal to eliminate #[should_panic], but test_serdes_bad_pk panics as intended - so it either should be rewritten to test the same case without panic - or perhaps it can
Surprisingly performance of --release configs is quite ok and on par with default desktop/leptop targets 👍
cool! @vhnatyk
I merged your code without the wasm specific part from this pr.
What do you think about adding this code in a folder in master branch and adding a readme with instructions on how to use?
@omershlo Here in this draft PR is only WASM specific diff to dev/vhnat/secp256-clean that is PR #6
You can run tests in wasm in chrome using wasm-pack with
wasm-pack test --chrome --release
. Adding--node
argument will runt tests and/or on node.Test
test_serdes_bad_pk
is ignored for now on wasm. Unfortunately#[wasm_bindgen(catch)]
doesn't work as expected. More details here I rewrote one testtest_wrong_homo_elgamal
to eliminate#[should_panic]
, buttest_serdes_bad_pk
panics as intended - so it either should be rewritten to test the same case without panic - or perhaps it canSurprisingly performance of
--release
configs is quite ok and on par with default desktop/leptop targets 👍