Allow calling Rust from hacspec #[unsafe_hacspec] about hacspec HOT 4 OPEN

With #105 merged, what is the status of this? What would still need to be done?

from hacspec.

So what you can do right now is to add an attribute to a function such that it will be ignored by the typechecker

Essentially what the Readme here says https://github.com/hacspec/hacspec/tree/a9f098d3a7f0adf40b37b289692324ec84c75bed/utils/attributes#hacspec_unsafe

But I'm not sure whether the import of non-hacspec crates works with this setup.
It should, because the typechecker doesn't look into other crates at all. But I don't think anyone ever tested this.

So it might all work already as expected but someone should test it (and ideally get a test in here so we can be sure it does). Then we can close this issue (or fix any issues we run into).

from hacspec.

There does not seem to be any code in the language crate related to hacspec_unsafe, so it only does something when running as part of rust code, not when exporting to backends. I am currently using cfg to exclude code from being seen by hacspec, but this also requires some checks in the backend, and making hacspec run with a cfg(feature="hacspec").

from hacspec.

There does not seem to be any code in the language crate related to hacspec_unsafe, so it only does something when running as part of rust code, not when exporting to backends.

Right, that's what it is supposed to do 🙂 The typechecker should ignore these functions. What do you expect it to do?
You could generate function stubs for functions that only have #[hacspec_unsafe] (as their signature should is in hacspec).

from hacspec.