Carlos O'Ryan
Carlos O'Ryan
Add `#warning` directives and start a timer to remove them.
I updated the files and announced they will be removed around 2023-01-01
Still waiting for the passage of time.
We should do this at some point.
Strike 2, we still want to do this.
It should be possible to split the LRO into a `*Client::SubmitFoo()` function, returning a `future` and a `AwaitFoo()` overload set, returning `future` and consuming either `StatusOr` or `future`.
Some ideas on this. Where today we have something like: ```cc future CreateBackup( google::spanner::admin::database::v1::CreateBackupRequest const& request, Options opts = {}); ``` In the future we would have two new functions:...
> Presumably that `StartCreateBackup()` returns something more like `future` than `future`. Doh! Fixed.
> I think that still begs the question of how `CreateBackup()` should behave when `AwaitCreateBackup()` exhausts its polling policy. It does. One answer is "The same way it does right...