Didn't your compiler warn you?
I think it did, this one wasn't too difficult to fix. But it happens quickly that a warning is overlooked (or not generated), especially with build systems like CMake...
But that's not the case with the 2.0 version right now and until it is - don't promote 2.0.
A lot of tutorials for SFML 2 are already online, but I agree the status quo without one for the Graphics package is not ideal. However, using a completely outdated version which is not maintained, contains fewer features and more bugs,
while there exists a better one, is not the way to go, either.
You also consider only the short term. Learning SFML 2.0 may be a little bit harder than 1.6 - but the additional time is invested
now and
only once. When you learn SFML 1.6, and then decide to port existing code to SFML 2.0 in a year, you have to re-learn a lot, and depending on your projects you have a big effort to make things working with version 2. Some modifications may require bigger refactoring, and you are already far behind the minimal time savings you had in the beginning.
Anyway, it is not that SFML 1.6 and SFML 2.0 are an equivalent choice, so only the learning time is a relevant criterion -- don't forget the massive amount of development that has been put into the library during these years. As a beginner, it may seem irrelevant, but as soon as you use more complex features or stumble upon bugs fixed long ago, you would be glad if you had begun with SFML 2.
