After a deeper discussion with friends in the Slack #cpp channel, we reached
the following consensus:
• iceberg-rust won't maintain any c/cpp related code.
• iceberg-cpp will have an internal crate based on iceberg-rust and invokes
cxx/cbingen to build bindings
• And finally, we will have a `l
> Would this property cause streaming writes using equality deletes to fail
until the table is updated? I’m open to this solution since I think people
should definitely be aware of the trade-offs they’re making in their tables.
I don't think we can do such a check on the Iceberg side. As discussed
