g++: TWENTY SCREENFULS WORTH OF ERRMES.

the mistake: `v=ptr` should be `v=*ptr`.

dude whenever someone says anything about idiomatic ceepluesplues I'ma just SLAP EM WITH A FISH~

C++''s error printing is very barebones, it basically tells you where the type solver got stuck. Nice error printing is really hard so I don't really blame them, but I think it would be worth some more attention.

It also happens that most of the times errors cascade. A single missing semicolon can lead to another dozen messages.

It gets real bad whenever templates get involved, but they've made significant progress with that, at least where the STL is concerned.

And, even if risking a fish slap, just use a shared or unique smart pointer, or if used as argument or similar, a owning_ptr<> or non_owning_ptr<> from the GSL. They resolve to regular pointers anyway and help a lot with pointer ownership and management.

@CoreFusionX cannot fishslap -- unique ptr is nice, I like the concept that memory should be deallocated when the owner goes out of scope as it simplifies things. I use my own class for it though, just because.

HMmm @retoor who should I slap with a fish? @donkulator is giving me ideas

@retoor but they like that and run off with the fish