-
Notifications
You must be signed in to change notification settings - Fork 230
Open
Description
Rustler is quite mature now and thanks to its great documentation it's easy to get a project working without reading the official erl_nif docs, which unfortunately means that users might not be aware of the big warning box there. While rustler can help eliminate memory errors, the warning about lengthy work is still just as valid, and for many projects, finding a way to do lengthy work correctly will end up being the most challenging part of writing a NIF. I think it would be helpful to:
- Add a warning to the rustler readme with a link to the erl_nif docs
- Link to the ways rustler supports the strategies mentioned in the erl_nif docs
- Threaded NIFs
- Dirty NIFs
- And Yielding NIFs once schedule_nif improvements #232 lands
evnu and narup
Metadata
Metadata
Assignees
Labels
No labels