Increment version and clean up some things

Author: SimonMaracine

README.md

@@ -8,7 +8,7 @@ that the reference increments and decrements are not atomic. The premise is that
 can be very useful in contexts outside of multithreading, in which atomicity is not needed, being just useless
 overhead. This is why I tried making my own version of `std::shared_ptr`.
 
-Right now, `shared_ref` doesn't fully conform with the `std::shared_ptr` specification of `C++17`. This is probably
+Right now, `shared_ref` doesn't fully conform to the `std::shared_ptr` specification of `C++17`. This is probably
 an incomplete list of missing features from my version:
 
 - Not allocator-aware

src/cpp_shared_ref/memory.hpp

@@ -16,7 +16,7 @@ namespace sm {
         bad_weak_ref(const bad_weak_ref&) noexcept = default;
 
         const char* what() const noexcept override {
-            return "Shared pointer construction failed, as weak pointer is empty";
+            return "Shared pointer construction failed, as weak pointer manages no object";
         }
     };
 }
@@ -74,7 +74,6 @@ namespace sm {
             ptr = ref.ptr;
             block = ref.block;
 
-            // We just created a new strong reference
             block.base->strong_count++;
         }
 
@@ -634,7 +633,6 @@ namespace sm {
                 ref.ptr = ptr;
                 ref.block = block;
 
-                // We just created a new strong reference
                 block.base->strong_count++;
             }
 

src/cpp_shared_ref/version.hpp

@@ -2,6 +2,6 @@
 
 namespace sm {
     inline constexpr unsigned int VERSION_MAJOR {0u};
-    inline constexpr unsigned int VERSION_MINOR {2u};
+    inline constexpr unsigned int VERSION_MINOR {3u};
     inline constexpr unsigned int VERSION_PATCH {0u};
 }