Work around issue 22619 - Avoid Nullable copy ctor unless required

Copy ctors are still buggy, so unconditionally adding one for Nullable
is everything but a non-breaking change (and was added in the 2.098.1
point release).

std/typecons.d

@@ -2792,7 +2792,17 @@ struct Nullable(T)
         }
     }
 
-    this (ref return scope inout Nullable!T rhs) inout
+    static if (__traits(hasPostblit, T))
+    {
+        this(this)
+        {
+            if (!_isNull)
+                _value.payload.__xpostblit();
+        }
+    }
+    else static if (__traits(hasCopyConstructor, T))
+    {
+        this(ref return scope inout Nullable!T rhs) inout
         {
             _isNull = rhs._isNull;
             if (!_isNull)
@@ -2800,6 +2810,7 @@ struct Nullable(T)
             else
                 _value = DontCallDestructorT.init;
         }
+    }
 
     /**
      * If they are both null, then they are equal. If one is null and the other
@@ -9546,13 +9557,28 @@ unittest
     {
         int b;
         @disable this(this);
-        this (ref return scope inout S rhs) inout
+        this(ref return scope inout S rhs) inout
         {
             this.b = rhs.b + 1;
         }
     }
 
     Nullable!S s1 = S(1);
+    assert(s1.get().b == 2);
     Nullable!S s2 = s1;
-    assert(s2.get().b > s1.get().b);
+    assert(s2.get().b == 3);
+}
+
+@safe unittest
+{
+    static struct S
+    {
+        int b;
+        this(this) { ++b; }
+    }
+
+    Nullable!S s1 = S(1);
+    assert(s1.get().b == 2);
+    Nullable!S s2 = s1;
+    assert(s2.get().b == 3);
 }