Skip to content

Split current "unsafe" chapter, cover more topics #112

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

Closed
5 tasks
japaric opened this issue Jun 17, 2014 · 4 comments
Closed
5 tasks

Split current "unsafe" chapter, cover more topics #112

japaric opened this issue Jun 17, 2014 · 4 comments

Comments

@japaric
Copy link
Member

japaric commented Jun 17, 2014

The current chapter needs to be split:

  • intro: What does the unsafe block means? (can't be proved safe by the compiler), should be used sparingly, first suspect in case of a segfault, should be treated as a red flag by the code reviewer
  • Dereferencing raw pointers
  • std::mem::transmute raw pointers -> references
  • asm!

We probably want to add:

  • static mut
@japaric japaric mentioned this issue Jun 17, 2014
52 tasks
@japaric japaric changed the title Topics for the "unsafe" chapter Split current "unsafe" chapter, cover more topics Jun 18, 2014
@steveklabnik
Copy link
Member

I'd be happy to mentor anyone who wants to work on this!

@crazystylus
Copy link

Hi @steveklabnik ,
Are you still willing to mentor someone one this?
I want to give it a shot!!

@steveklabnik
Copy link
Member

Sadly, I am not. @marioidival is the only person left working on rust by example. He may, or he may not. Good luck!

@marioidival
Copy link
Member

Hi, I'm closing this issue just to clean up the items that already exist. If you think this issue makes sense to stay open, please create a new issue with updated information and mention this one.

thanks!

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

No branches or pull requests

4 participants