There's a bunch of methods in QgsVectorLayer and QgsVectorDataProvider which are not marked as const, but should be: eg:
QgsVectorLayer::getFeatures
QgsVectorLayer::minimumValue
QgsVectorLayer::maximumValue
QgsVectorLayer::getValues
QgsVectorLayer::getDoubleValues
QgsVectorLayer::uniqueValues
(and their QgsVectorDataProvider counterparts)
This would also require const correctness of QgsVectorLayerEditBuffer - some methods such as QgsVectorLayerEditBuffer::addedFeatures return a const list but are not marked const themselves.
Some of this could possibly be fixed pre 3.0 (eg the edit buffer changes), but the required provider changes constitute an api break
nyalldawson
commented
7 years ago
There's a bunch of methods in QgsVectorLayer and QgsVectorDataProvider which are not marked as const, but should be: eg:
(and their QgsVectorDataProvider counterparts)
This would also require const correctness of QgsVectorLayerEditBuffer - some methods such as QgsVectorLayerEditBuffer::addedFeatures return a const list but are not marked const themselves.
Some of this could possibly be fixed pre 3.0 (eg the edit buffer changes), but the required provider changes constitute an api break