Closed adamierymenko closed 1 year ago
I believe this might might be caused by build script conflicts?
Anyway can put this in to get stack unwinding for you, but would go the other way: enabling std rather than no_std.
Automatically closed by the PR but let me know if there is still any problems using the std
feature from the master branch and I will reopen it.
Looking to roll this up into a version 0.4 release by the end of the week. Thanks :)
You get this, which after a dive into a rabbit hole seems caused by no_std. Commenting out the no_std directive in
lib.rs
gets rid of this. Note that I am usingreference
so no AVX2 errors are involved.no_std
should maybe be a feature flag?