Implement `Debug` for public types

[tmccombs]

Fixes #427.

I included what I though was important in the implementations, but I'm open to suggestions.

[nikomatsakis]

@tmccombs hmm -- I'm seeing a bunch of travis failures! do you mind taking a look?

[KodrAus]

That'll be the deny(missing_debug), which includes pub structs even if they aren't re-exported.

@nikomatsakis would you rather keep the lint and work around pub(not pub) structs or just remove it?

[tmccombs]

Ah I didn't run with rayon_unstable feature turned on locally. I'll look into them.

[tmccombs]

hmm, I had a typo, so it didn't actually get everything, I'll work on getting all the structs I missed.

[KodrAus]

Thanks @tmccombs! There's been a lot of structs to add Debug impls for.

This looks good to me.

[KodrAus]

Thanks @tmccombs! There's been a lot of structs to add Debug impls for.

This looks good to me.

[KodrAus]

This could probably just be fmt.debug_struct("RayonFuture").finish().

[KodrAus]

I'm happy with this, so I'll hand over to @nikomatsakis or @cuviper who might want to tweak the fields included for some of the Debug implementations.

[KodrAus]

I'm happy with this, so I'll hand over to @nikomatsakis or @cuviper who might want to tweak the fields included for some of the Debug implementations.

[cuviper]

I think probe() will always be true until the scope is out of the user's hands. For debugging purposes, the actual counter value would be more interesting. How about adding Debug to CountLatch and show that here?

[tmccombs]

alright

[cuviper]

I added a couple more that hit master in the meantime.

Thanks!