-
Notifications
You must be signed in to change notification settings - Fork 20
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
unsafe
blocks
#417
Comments
This issue has been marked as stale due to a lack of activity for 60 days. If you believe this issue is still relevant, please provide an update or comment to keep it open. Otherwise, it will be closed in 7 days. |
Great timing of the bot, this should also go on https://github.com/cryspen/home/issues/95 I suppose @W95Psp |
Basic support was added in #867. I wonder if we should just turn the unsafe feature on in the F* backend then. Wdyt @franziskuskiefer? |
Sure, let's turn it on for F* and see what happens. |
No, more advanced support would mean library support in the backends, so we should close that issue. |
This PR follows from #417 (comment), and from PR #867. It turns on the `unsafe` feature for the F* backend.
We don't plan to support
unsafe
blocks.The text was updated successfully, but these errors were encountered: