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

> the history of closures in Rust is a long and convoluted one, with many dead ends and failed experiments.

I desperately hope that someday, when all the dust settles, someone writes an account of this and other long and winding paths Rust has taken through its evolution, so people in the future can get the benefit of this wisdom. An account of dead ends could make for fascinating reading.

The trick would be putting in just the right amount of detail. Enough so the reader can truly understand the reasoning behind why things worked (or didn't) without being so dense as to be unreadable.



Being Lazy With Class is something like that, but for haskell, and is indeed really interesting to read:

http://haskell.cs.yale.edu/wp-content/uploads/2011/02/histor...


Yeah, that would be great and easier than reading through huge archives of mailing lists probably.


maybe Steve Klabnik will accept this challenge ;)




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

Search: