André Somers schreef op 21-8-2014 16:33: > Thiago Macieira schreef op 21-8-2014 16:14: >> I'd like to deprecate QVariant's internal >> nullability concept and make it rely on carrying a QOptional for a type to be >> null. >> >> If we don't do that, then QVariant: of a QOptional<QString> could be: >> >> 1) a null QVariant >> 2) a non-null QVariant containing a null (disengaged) QOptional >> 3) a non-null QVariant containing a non-null (engaged) null QString >> 4) a non-null QVariant containing a non-null (engaged) non-null QString >> >> That's just non-sense and confusing to me. I'd like to collapse 1-3 as much >> as >> possible. > I assume you also want to remove the nullability of QString then? > In both cases, you're going to break *a lot* of code. Just to continue along that path a little bit...
If you type isNull in the index box of the Qt offline help, you really get a huge load of classes that have the isNull function. All of those should be deprecated then? André _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
