Nick Cameron

1.0 release

2

- [x] test where clauses - [x] tuple structs - [x] stable macros 1.1 - [x] Set up travis build - [ ] Polish up the readme a bit, add...

Consider API

1

Spend some time making sure the API is optimal - in particular the naming of functions

Should wrap one of the temp file/dir crates and provide an easy to use API for this.

At the least we should mention the filename for file errors

There should be a short guide in the README (and libs docs) to show users what can be done with the crate and the different ways it can be used

There should be more examples in the docs, these are currently missing

Should be easier to implement in ezio than in the general case because we don't need to worry about error handling or optimal performance. Something like the following should work:...

I think the ezio types should all be able to implement `BufRead` as well as `Read`. Probably it will need to be a bound on `ezio::Read` to be useful.

Add implementations of `Read` for `&Reader`, etc., following `File` in std. This is not straightforward because the std trait functions require `&mut self`, so we either need to keep references...