Skip to content
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.

Sign up for GitHub

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

Jump to bottom

safe/unsafe support #144

Closed
wavewave opened this issue Nov 17, 2019 · 0 comments · Fixed by #229
Closed

safe/unsafe support #144

wavewave opened this issue Nov 17, 2019 · 0 comments · Fixed by #229
Labels
New Feature
Projects
dev

Comments

@wavewave
Copy link
Owner

By default, fficxx generate FFI code as safe FFI. However, for performance, it is desirable to allow users to specify unsafe for a certain methods. Make this opt-in.
@wavewave wavewave added this to Backlog in dev Nov 17, 2019
@wavewave wavewave linked a pull request Aug 28, 2023 that will close this issue
FFI safety is now explicitly given #229
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
New Feature
Projects
fficxx dev
Status: Done
dev
  
Backlog
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

FFI safety is now explicitly given wavewave/fficxx
1 participant
@wavewave