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

no_std? #2

Open
Michael-F-Bryan opened this issue Feb 19, 2017 · 0 comments
Open

no_std? #2

Michael-F-Bryan opened this issue Feb 19, 2017 · 0 comments

Comments

@Michael-F-Bryan
Copy link
Owner

could we somehow make option 2 safer by using #[no_std], because that tells rust that there is no allocator that we can accidentally use. Or is that overkill?

(Original Question)

Look into whether you could use #[no_std] to make things safer or more convenient to do FFI (because there are less features to worry about).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Michael-F-Bryan