Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

That’s perfectly reasonable if you’re writing lots of parallel code, but frankly 95% of web server code isn’t the sort of hairy parallel code that would benefit from a borrow checker on balance.



There are no threads in this scenario. You can easily lose ownership / crash on bad references when using golang maps in a single thread.


How do you get "bad references" in a Go map in a single thread? Are you thinking of nil pointers? That's a separate issue.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: