is there a good example of creating a python

datatype

from scratch in rust code?

we usually call the function

create_*

that we get when initializing the scheduler, and provide arguments to that

ah, like

construct_directory_digest

?

yes!

related question: how much extra stuff on top of the standard rust futures crate is pants using?

future::ok()

, which may already be available as

ok()

depending upon which file you're in

like, if there are any pants-specific macros or what have you that are used pervasively around the crate imports

i don't think so

ok

like there's

future::ok()

and then you just

.map()

,

.and_then()

, and then you have to call

.to_boxed()

at the end to make it a

BoxedFuture

Magic on top we have: •

BoxFuture<Item, Error>

is just an alias for

Box<Future<Item=Item, Error=Error> + Send

•

try_future!

is like the

try!

macro (which is the same as the

?

operator), but which returns a

BoxFuture

rather than a

Result

(i.e. if its argument is an error, it early-returns a

BoxFuture<_, Error>

of that error, else it unwraps the

Ok(T)

to a

T