Laurențiu Nicola

So we can add `fn set_field_by_index(&self, idx: usize, value: &FieldValue)`, `fn set_field_integer_by_index(&self, idx: usize, value: i32)` and about 9 more. But I'm worried that users will just do: ```rust for...

Ping @aljen can you take another look at this?

Looks pretty good, but I only checked the first two commits.

I do wonder, though, if we shouldn't go straight for `GDALWarp`. It's not that much harder to use, and I think that mailing list reply suggested that it's the most...

No, they're checked for collisions. Not saying it's because of your changes, I just didn't see it before.

It's a lot of work to write the bindings for, it's similar to gdaldem.

Hmm, I was able to reproduce the crash on `master`, so it's not #510. The "Layer new already exists" message points to the `poly.gpkg` tests, which we should fix. However,...

``` #0 0x00007ffff768dfcb in OGR2SQLITEModule::Setup(sqlite3*) () from /lib64/libgdal.so.33 #1 0x00007ffff768e7d5 in OGR2SQLITE_Setup(GDALDataset*, OGRSQLiteDataSource*) () from /lib64/libgdal.so.33 #2 0x00007ffff797d9fb in OGRSQLiteDataSource::OpenOrCreateDB(int, bool) [clone .constprop.0] () from /lib64/libgdal.so.33 #3 0x00007ffff7656825 in OGRSQLiteDataSource::Open(GDALOpenInfo*)...

They should be dynamically linked. I think SQLite is pretty robust, at least in some build configurations (unlike.. ahem.. netcdf). And I couldn't trigger it when filtering by `layers` (or...

I still had gdb running, so I checked the other threads: ``` (gdb) info thread Id Target Id Frame 1 Thread 0x7ffff1b5cf40 (LWP 509695) "gdal-0978520db0" 0x00007ffff66526ed in clone3 () from...