forked from qt-creator/qt-creator
Sqlite: Workaround an over-constraint in GCC 10
Restores GCC 10 compatibility. std::input_or_output_iterator is over-contrainted in GCC 10. It wants a default constructor that is not specified: https://en.cppreference.com/w/cpp/iterator/input_or_output_iterator Adding a default constructor works around the defects. Change-Id: I2a2456df96f92c0d2b920f90dce8e7656c8905bb Reviewed-by: Tim Jenssen <tim.jenssen@qt.io>
This commit is contained in:
@@ -458,6 +458,7 @@ public:
|
|||||||
using pointer = ResultType *;
|
using pointer = ResultType *;
|
||||||
using reference = ResultType &;
|
using reference = ResultType &;
|
||||||
|
|
||||||
|
SqliteResultIteratator() = default;
|
||||||
SqliteResultIteratator(StatementImplementation &statement,
|
SqliteResultIteratator(StatementImplementation &statement,
|
||||||
const source_location &sourceLocation)
|
const source_location &sourceLocation)
|
||||||
: m_statement{&statement}
|
: m_statement{&statement}
|
||||||
@@ -510,8 +511,8 @@ public:
|
|||||||
value_type operator*() const { return m_statement->createValue<ResultType>(); }
|
value_type operator*() const { return m_statement->createValue<ResultType>(); }
|
||||||
|
|
||||||
public:
|
public:
|
||||||
StatementImplementation *m_statement;
|
StatementImplementation *m_statement = nullptr;
|
||||||
const source_location *m_sourceLocation;
|
const source_location *m_sourceLocation = nullptr;
|
||||||
bool m_hasNext = false;
|
bool m_hasNext = false;
|
||||||
};
|
};
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user