You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was writing a wrapper for a few functions in QStandardPaths which I need and a question popped up in my mind. Many Qt functions return a null QString (not to be confused with empty QString) when the value cannot be found. In such cases, should the bindings return Option<QString> instead of QString?
Similarly, most Qt functions will return empty QList when nothing is found. So I would like to hear everyone's opinions about using Option in the return type of such functions.
The text was updated successfully, but these errors were encountered:
I was writing a wrapper for a few functions in
QStandardPaths
which I need and a question popped up in my mind. Many Qt functions return a nullQString
(not to be confused with emptyQString
) when the value cannot be found. In such cases, should the bindings returnOption<QString>
instead ofQString
?Similarly, most Qt functions will return empty
QList
when nothing is found. So I would like to hear everyone's opinions about usingOption
in the return type of such functions.The text was updated successfully, but these errors were encountered: