New Frontend™ progress report

[Hamcha]

Since I used the Erlang frontend as an example while doing Goleg and now it's gone, I'd like to know what's needs to be done so I know what to do and when the new frontend will be ready for merging.

Missing Features

• ~~Basic Get/Set~~ a6e7067
• ~~Cursor iteration~~ 4b21c97 6d6ed73
• ~~Prefix matching~~ 7dca943 ef54951 3f04060
• CAS support

Other stuff

• ~~Sample config~~ a6e7067
• ~~Updated makefile~~ a6e7067
• Frontend Tests (Check #127) IN PROGRESS 0f7db08 a603f16
• ~~Force linking against local library~~ 349d3bb
• ~~Update olegdb.org documentation with API changes~~ 2ac3071

Tell me if I forgot something.

As I said on IRC, if you think we should edit how the API work, speak up, it's better to decide before I implement stuff.

[qpfiffer]

It was never implemented in the Erlang frontend, but I'd like support for cas, too.

Edit: Another awesome thing to have would be frontend tests, we currently have none.

[Hamcha]

I don't know Travis' status for Go stuff, so it'd be best if you do those settings yourself, my buildbots have all Go installed, so it shouldn't be a problem. I'll see what I can do with testing…

[kyleterry]

I can setup the travis stuff, I've already done it for tenyks.

[qpfiffer]

Testing ticket here

[kyleterry]

Now with thread safety™