5 ms·
The book appears to be promising, but it is still far from being complete and doesn't touch the main points of interest, such as inheritance and problems arisin
by geezerjay 10y ago
The book appears to be promising, but it is still far from being complete and doesn't touch the main points of interest, such as inheritance and problems arising from any form of template specialization.
Perhaps the author could get the book up to a presentable point before advertising it.
- jhoechtl 10y agoThere was a rant earlier this week in the same vain: Instead of presenting something pre-mature check back later once its done. I think it is still wothwhile to present something you have instead of waiting once its done. Also the understanding "once its done" varies from the use case. This in your opinion unfinished book might be of use to others. It is also good to have something written and share it with others to get feedback (as you did) at an early stage.
- e12e 10y agoIs there any indication that the hn submitter "ingve" and the github owner "locka99" is the same person? For that matter, the author might want to put his/her name on the book - I couldn't find anything in either the foreword or credits section.
- bluejekyll 10y agoOr maybe they're trying to get more community support for it?
- tom_mellior 10y ago> doesn't touch the main points of interest Including how to port code from C or C++ to Rust, i.e., what it claims to be. So far this is an OK overview of Rust's advantages over C and C++, but very very little of it is an actual "guide" to porting stuff.