cpp-from-the-sky-down VS iface

If you are looking for a simple solution for inbox zero for gmail - quickly classify emails as archive, follow-up, read through, take a look at my hacky attempt.

https://github.com/google/cpp-from-the-sky-down/blob/master/...

It is inspired by vim. It downloads all the email snippets and sorts them in descending order by sender and date.

Then you use “j”, “k” to navigate through the emails. You can press “a” for archive, “f” for follow up, and “r” for read through. You can also press “p” to navigate to next email prefix (the stuff before the @) and “d” to navigate to the next domain. Like vim you can combine keystrokes. “ad” will archive all the emails from the present position to the next domain. Since these are sorted by reverse date, often you can look at recent dates and archive the rest.

All operations happen in memory so they are instantaneous. You the press “w” to actually move the messages on the server as a batch operation.

It is really useful if you are getting started or are falling behind and need to quickly classify a few thousand emails.

It is a single 500 line Rust program so you can hack on it to change it to how you like it.

>The generated code always checks the various return codes and always uses the correct column ordinals and column types when binding or reading data to or from the SQLite system — areas that are notoriously difficult to get right and keep right.

If you care mostly about this part, and are using C++20, you can use meta programming to accomplish this with some annotations of your SQL statements, and avoid code generators and separate syntax.

https://github.com/google/cpp-from-the-sky-down/blob/master/...

        ftsd::prepared_statement<

I am using sqlite as the database via rusqlite. I am using my own project: tagged_rusqlite (cpp-from-the-sky-down/rust/tagged_rusqlite at master · google/cpp-from-the-sky-down (github.com) ) on top of rusqlite for strongly typed rows and query params.

The full code is at: https://github.com/google/cpp-from-the-sky-down/blob/master/rust/

cpp-from-the-sky-down/example.cpp at master · google/cpp-from-the-sky-down · GitHub

I think I do it differently. In iface, if the copied-from interface instance concerns a superset of the contract that the interface being constructed does, I will point to the matching subrange (line 195 in particular here). Otherwise I add another layer of indirection.