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.

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

Rust #361

Open
Surysingh opened this issue Nov 8, 2022 · 5 comments
Open

Rust #361

Surysingh opened this issue Nov 8, 2022 · 5 comments

Comments

@Surysingh
Copy link

Rust has lot of features which can help prevent common memory related issues. Recently Linux Kernel is also moving towards Rust.

Is there any plan for LK to also use Rust?

Thank you.

@travisg
Copy link
Member

travisg commented Jan 16, 2023

I've spent some time this last holiday learning some rust and it is definitely something that could be done. The hard question is defining exactly how to fully integrate it into the system. ie, which direction can apis call? Is it okay to define a rust module that C code calls into, or is it more of a C -> Rust as some sort of leaf node library.

@GravisZro
Copy link

Rust would be a poor choice because it doesn't support all the target architectures.

@Surysingh
Copy link
Author

Rust would be a poor choice because it doesn't support all the target architectures.

Which target architectures are not supported in Rust? We can still have conditional build to use rust for supported architectures?

@Surysingh
Copy link
Author

Surysingh commented Jan 25, 2023

code

Thank you for the reply.

For example, the memory manager like dlmalloc written in Rust, the malloc-free api users are written in say C/C++, then the benefits offered by rust, will no longer apply in C program. So would it be very effective, is this the question being considered?

@kanakshilledar
Copy link

Are there any plans of moving towards rust?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants