I'm not enthusiastic about endorsing .ok().expect(...)...

Hum... Any particular reason ?

It works here because our error type is () but generally is inferior to Result::expect and seems the opposite of idiomatic. People will use pieces of our examples without questioning them. Maybe we should replace the panic with print! and return.

I'd prefer this actually. I'm not a big fan of panic! when it's not absolutely necessary.

We should start by updating the actual example(s) anyway and then bring the change here.

Actually, it doesn't seem to be a priority but if you have nothing else waiting, then I let you update examples. ;)

I'm working on push some hand-generated docs after that maybe.

As you wish, I'm starting to prepare to push on crates.io tomorrow.

I've found a little issue with the version handling and enums in cairo. Might want to hold off pusblishing crates a bit.

Ok, I'm in standby. Just email me when the situation is unlocked please. ^^

I've just learnt more about the issue. Good news is, it's not a crates showstopper.

Turns out rustdoc doesn't get the same cfg directives rustc gets so it can't see any of the gated stuff. WAT

DARK MAGIC !!!
Well, I work on crates tomorrow now. Witches will wait !

Looks like we've resolved this in a different way.