Do not use flat_set anymore gives compilation issues.
Not worth the time solving the issue without having prove of a clear benefit of using flat_set over unordered_set.
This commit is contained in:
parent
1854a4bdaa
commit
6a2c8ec5e0
5 changed files with 13 additions and 11 deletions
|
|
@ -9,7 +9,7 @@
|
|||
#include "CustomDataRole.h"
|
||||
#include "PgLabItemDelegate.h"
|
||||
#include <QStringBuilder>
|
||||
#include <boost/container/flat_set.hpp>
|
||||
#include <unordered_set>
|
||||
|
||||
TriggerPage::TriggerPage(QWidget *parent)
|
||||
: QSplitter(Qt::Vertical, parent)
|
||||
|
|
@ -55,7 +55,7 @@ void TriggerPage::setFilter(const std::optional<PgClass> &cls)
|
|||
void TriggerPage::tableView_selectionChanged(const QItemSelection &/*selected*/, const QItemSelection &/*deselected*/)
|
||||
{
|
||||
auto&& indexes = m_tableView->selectionModel()->selectedIndexes();
|
||||
boost::container::flat_set<int> rijen;
|
||||
std::unordered_set<int> rijen;
|
||||
for (const auto &e : indexes)
|
||||
rijen.insert(m_sortFilterProxy->mapToSource(e).row());
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue