-
Notifications
You must be signed in to change notification settings - Fork 51
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
Fix features #238
Fix features #238
Conversation
This breaks the release action that runs on the main branch: |
Yeah, will fix, do you otherwise agree it is better to remove those features though or should provide more details? |
AFAIK runtime detection costs a bit of performance, can't recall if is it noticeable. If that's true, then we may leave option for user to force settings instead of runtime detection. |
c-kzg-4844 removed features for |
There is no runtime cost, it is all decided at compile time.
|
Interesting, I thought they added runtime detection recently supranational/blst#10. |
Looks like they are only used in portable builds, so compiling without selecting portable flag should give you the same result as before. |
Is there anything else I should do here? With this we should finally be able to use upstream version of this library at Subspace Network, had to patch it all along prior to this. |
Seems it broke the build. I'm reverting. |
Looks like |
First commit removes features of
blst
that shouldn't be necessary (and shouldn't exist inblst
in the first place) as described in #233 (comment).Second commit fixes regression from #232 that caused
hex
dependency to pull standard library in (annoyinglywasm32-unknown-unknown
does have a standard library, although an incomplete one, so it didn't cause CI failure).