Fail on/remove library functions that are not in hacspec about hacspec HOT 3 OPEN

Hi Franziskus, I'm afraid this one is going to be difficult to do.
i) if we split into two crates, we'll run into the Rust limitation that you can't implement a trait or make an impl block for a type that is not defined in your crate
ii) we can't retrieve the #[not_hacspec] attribute in external crates metadata, the attributes are compltely erased

The solution for enforcing this is to generate additional .json files containing a whitelist of functions in Hacspec, but this is a heavy machinery to implement and I didn't have the time to do it yet.

from hacspec.

Yeah, I just ran into this and figured that this is pretty bad user experience. I don't know if there's a low effort way to fix this. But we should have it on the list to fix.
Another idea would be to build the dependencies as part of cargo hacspec and compile out all functions with #[not_hacspec]. Then this would fail in the Rust build system already.

from hacspec.

Another idea would be to build the dependencies as part of cargo hacspec and compile out all functions with #[not_hacspec]. Then this would fail in the Rust build system already.

Hum it would not work with cargo hacspec but cargo build. You could feature-out the non-hacspec parts of hacspec lib. But then you could not include the testing code that needs the non-hacspec parts in the same crate.

from hacspec.