Chris Thrasher

What I'm gathering is that `sf::LineShape`'s inclusion hinges on us crafting a better, more complicated abstraction for prebuilt shapes. I'm happy to get into that but I think a better...

Fixed minor merge conflict.

Rebasing to keep up with `master`. No changes.

Fixed trivial merge conflict.

Rebased and reformatted because of #2159

Rebased and fixed compiler error.

Rebased because it's been a while and because I needed to convert some `size_t`s to `std::size_t`s.

Rebased to catch up with `master`. No changes required.

To be clear, nobody is advocating for _every_ class having a string representation nor even most classes having it. We just need a handful of types to support it. Currently...

I don't think anyone is advocating for adding member functions. Why in a separate header though? More compile time concerns?