I added a link the recording of today’s libs team meeting about
I wrote a summary of the meeting.
Can I suggest glob/globset? I believe
globset is the way forward but it would make sense to transition the
glob crate to be
Thanks for the suggestion @Keats! Seems like the right kind of crate, though I’m not familiar myself.
So far our crate tracking issues have not had a “Release 1.0” issue actually filed, but I kind of think they should. I might go back and do that and link up the tracking issues. Any opinions?
There’s some question about whether it makes sense to include mio in the cookbook as it is a low level systems-integration piece.
Rust Libz Blitz status update 2017-06-02
Here’s what is going on in libz blitz news this week. Spoiler alert: it was another great week! Thanks everybody.
Upcoming we’ll expect @aturon to open the error-chain evaluation soon. It also looks like we need to get someone on the hook to lead the mio evaluation to get that evaluation started by 6/11.
I’m also interested in getting some of the “out-of-band” evaluations going, crates like idna, net2, unicode-segmentation, env_logger. We can run these exactly as we do the others, but we just won’t schedule a libs team meeting to finalize them. Anybody interested in leading them just speak up. I may pick up one myself next week.
- @budziq updated docs to link to loggers
- @rap2hpoutre improved the max_level docs
- @jehiggs improved Location docs
- @MarkMcCasky improved Metadata docs
- @jehiggs improved Record docs
- @budziq improved added “Errors” to set_logger docs
- @nivkner improved set_logger_raw docs
- @rap2hpoutre added an example to set_logger
- @aergonaut added serde impls for LogLevel and LogLevelFilter
- @meven also added serde impls for LegLevel and LogLevelFilter!
- @alisha17 began changing set_logger to panic on error
- @nivkner updated ParseLevelError docs
- @nivkner renamed the error type
- libs team reviewed on 5/30, with the help of @seanmonstar, @KodrAus, and stephanbuys. video
- @dtolnay filed the tracking issue
- @tomprince hid internal conversions to reqwest::Error
- @tomprince made Error::get_ref return a Send + Sync error
- @seanmonstar converted RequestBuilder to an &mut self builder
- @theduke began moving the try_ macro
- @alisha17 converted examples to use ?
- @little-dude handled json serialization errors
- @budziq added html_root_url
Looks like the only remaining blocker is to rename internal types to match public types.
No activity this week but there are still issues open.
Looks like remaining work is blocked on questions about the API.
- @budziq added a note about OAuth to network examples
- @derekdreery added a memmap example
- @budziq added a thread pool example
- @jaemk put sheilds behind a cache
- @budziq added an example of custom headers and URL parameters
- @budziq added an example of consuming a paginated REST API
Tasks needing contributors
- log: Support construction of
- log: Expand log! docs for
- log: Maintaner wanted for env_logger
- reqwest: Expose RedirectAttempt and RedirectAction types
- reqwest: Add realistic examples for Response
- reqwest: Document Body constructors
- reqwest: Document Error
- reqwest: Add examples for
- url: Document percent_encoding module
- url: Implement Debug for many types
- url: Put error conditions in “Errors” sections
- url: Explain the term “fragment”
Personally I find tracking issues (for versions at least) to be more onerous, and so I assigned all the new issues in reqwest to a ‘v1.0’ milestone instead. The problem with tracking issues is you have to remember to check off issues as they’re closed, and you need to click through to each one to determine if you can check it off. Milestones are automatic.
I would like to suggest HTML parser crates html5ever or its very nice high level wrapper select. Both are sorely in need of documentation. There is already a nice select cookbook example waiting for merge.
Thanks for the suggestion @seanmonstar. I’m open to switching to milestones if that’s what others prefer. One thing we would lose there is a place to write comments about the overall progress, but I don’t know how important that is.
you could always have a ‘tracking issue’ that’s part of the milestone to keep comments and such things? it could link to the milestone rather than to each individual issue in it, and be closed off when the release is made or somesuch
I created a cookbook issue for flate2 / tar recipes: https://github.com/brson/rust-cookbook/issues/185
Due to a scheduling conflict I bumped mio to 8/15, and moved gcc up to 7/11.
Since we’re trying to open evaluations one month ahead of time, that means @burntsushi will need to open the gcc thread next week.
walkdir is scheduled for next Tuesday. Everything ready to go @KodrAus? Need any help still?
I added rayon and mime to on-deck evaluations. rayon is about ready for 1.0, and very popular. mime also gets around a lot and libs team has expressed interest. I demoted env_logger to out-of-band evaluations, as I don’t see the libs team revisiting logging any time soon. I’m still hopeful to get some such evaluations going soon.
The csv crate is also about ready for 1.0, and would be worthy of review. As a @burntsushi crate it’s going to be super high quality. I’m a little iffy about whether it is within the present mandate of this project, though certainly csv is a common format, and is sometimes supported by standard libraries.
csv: It’s at
1.0.0-beta.3 right now, which was intentional so that I could still make breaking changes. My plan is to probably get
1.0 out before the end of the year. I agree with your concerns @brson though, but I just wanted to put this out there!