3 ms·
I like it so far. Is there any sense of ordering, or is each article self-contained? I wouldn't encourage shared_ptr as the smart pointer of first resort, uni
by bcoates 13y ago
I like it so far.
Is there any sense of ordering, or is each article self-contained? I wouldn't encourage shared_ptr as the smart pointer of first resort, unique_ptr is preferable where it's suitable.
I would also suggest going ahead and giving more guidance on when and when not to use various features, C++11 has a lot of redundant features. This is gonna start shading into matters of opinion, but somebody's got to do it, and for a novice any sane advice is better than nothing.
- bloodorange 13y agoThanks for the feedback. I've divided the features into "high priority", "medium priority" and "low priority" categories. I am covering the "high priority" ones first in what I felt was decreasing order of priority. Also, I am doing one article one core language feature, then one on the library and continue alternating in that fashion. I like your idea on when we should use certain features and when it would be good to avoid them. I'll consider doing a few examples of that kind too. I think I'll do a few of those once I am done with a few samples form the "high priority" set that I mentioned in an earlier comment in this thread.