Hacker News new | past | comments | ask | show | jobs | submit login

I would say it depends. Maybe Walter will chime in, but from what I can tell it is fully possible to use raw pointers (-betterC) and step into unsafe space, but if you're using the full runtime it should be as safe as go, java, etc.



-betterC removes the druntime features, but pointer safety is gained with the -dip1000 flag (with @safe) regardless of whether you use betterC or not.

@safe will also stop you doing obviously unsafe pointer arithmetic unless you abstract it into a @trusted function.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: