Christof Leutenegger

I am kind of against it, I see the motivation but adding the extra keyword is in my opinion not much more convenient than just using `gdf.index += offset`.

Let's have this comment as am overview of everything we have and what we may need to work on before handing it in for review. ## Requirements ### Readme ❌...

Uff :D To be honest I am not quite sure if we can fix this one. Like most of our function depend on that we have the whole dataset in...

Currently we have 28 + (4 postgis) warnings, the sources are: - 7 future warnings that geopandas will remove setting crs on geodataframes without geometry - (4) from using geopandas...

For geopandas I know that they are hiding the dependencies in a version checker file [`_compat`](https://github.com/geopandas/geopandas/blob/main/geopandas/_compat.py) that sets some global flags. They just implement the same function in different versions...

Done in #422 :) As for the bug in #420. We probably would have to search in the space of possible numpy-pandas versions what could cause the bug (perhaps automatically)....

The only warnings we currently have is a deprecation warning for the pyproj, nothing we could influence. So I'll close this issue.

Here is a minimal testcase for this issue: ```rust fn main() { let _ = [0] == [0]; } ``` outputs: ``` thread 'rustc' panicked at minimize/src/bb.rs:205:25: unsupported Rust intrinsic...

The boolean comparison operators are also not supported yet: ```rust fn main() { let _ = false < true; let _ = false = true; let _ = false >...

On a similar note the comparison for pointers is also not supported: ```rust fn main() { let a = &42 as *const i32; let b = &21 as *const i32;...