Hi @brson/@burntsushi … I would like to work on out-of-band evaluations - “regex”. Is it still open and anybody working on it ??
If its closed, could you please point me where can I involve/contribute.
Thanks, Rufus C Sharma
AFAIK, nobody is working on it. Note that regex has already gone through the RFC process, but more evaluations can’t hurt!
Discourse permissions strike again!
I’ve opened a tracking issue for the same-file evaluation, but can’t update the OP because it mentions more than 10 users.
Could somebody with super-permissions please add that link in to the same-file evaluation in the other evaluations list? 
Thanks!
1 Like
All set, thanks!
I tried looking for a way to expand the permissions of the post (it is a wiki after all), but couldn’t see anything obvious. AFAIK, I have super duper powers, so maybe there isn’t a way!
1 Like
Thanks for closing out the same-file evaluation @KodrAus.
I’ve done the same for error-chain, and added both to the op’s help wanted section.
1 Like
I’ve also reviewed the state of the env_logger evaluation, trying to move it toward a close. There are a few questions about whether to expand its flexibility or not that need some feedback from the log maintainers before we move forward.
I removed some unimportant mentions so hopefully everybody can edit again.
1 Like
Hi the cookbook repo has been moved to https://github.com/rust-lang-nursery/rust-cookbook 
!
With rendered version available under https://rust-lang-nursery.github.io/rust-cookbook and repo to
Please note that only some of the old links are still functional due to github redirects, so it’s a good moment to update your bookmarks
1 Like
Status update 2017-08-08
This update covers the period from 7/14 to 8/8.
There are several ongoing evaluations:
-
randis undergoing discussion on an overhaul, led by @dhardy; this should lead to an RFC! - the
mioevaluation, led by @dtolnay, is up! - the
env_loggerevaluation, led by @sebasmagri, continues! - the
threadpoolevaluation, led by @ericho, continues! - the
same-fileevaluation, led by @KodrAus, continues!
Thanks to everyone who has been pushing these evaluations forward, and special thanks to @KodrAus and @dtolnay for their help coordinating the effort overall.
Next up is rayon, and a possible out-of-band evaluation for Diesel!
Overall check-in
We took some time to check in on how all of the evaluated crates are doing, and found that in general, things are in fantastic shape. Many crates are essentially complete and ready to cut a 1.0. Others need a final pass over documentation and cookbook examples, but are otherwise ready. Only a few still need significant work:
- error-chain, which will receive more attention during the impl period
- temp-dir, which may be merging with tempfile
- gcc, which was recently evaluated and has many open issues
The libs team hopes to write up detailed contribution guides for the upcoming impl period.
Work completed this cycle
Here’s what happened on crates since the last status report:
url
walkdir
- @AndyGauge added Error docs to Result-returning methods
- @meven added links to other walkdir items
- @AndyGauge added links to .into_iter() and .filter_entry() into respective Types
- @alisha17 corrected errors in WalkDir type docs
- @tmccombs added Debug for public structs
- @expenses added links to references in docs
- @KodrAus made WalkDir Send + Sync
- @shssoichiro documented why unwraps won’t fail
- @jeremielate removed re-export of is_same_file
- @KodrAus added a Unix-specific extension trait
gcc
-
@opilar added examples for
Config::targetandConfig::host - @AndyGauge added hyperlinks to internal methods/structs/functions within docs
- @opilar added readme and categories to Cargo.toml
- @AndyGauge changed compile to accept name of library and updated examples
-
@jehiggs clarified behavior of
expand -
@omh1280 removed
compile_librar - @chrisvittal added a note that the crate can compile assembly
-
@opilar added
Config::filesmethod
3 Likes
Small correction: These were just rebased from work @jeremielate did 
Hi, please do not forget about the work done by rust-cookbook contributors .
This was a fruitful period. Thanks to all involved!
Cookbook
- @luser Add an example of calculating the SHA-256 digest of a file using ring
- @yandexx Use a custom environment variable to set up logging
- @dhardy Basics: improve random number examples
- @yandexx Extract all unique links from a MediaWiki markup
- @AndyGauge Extract phone numbers from text
- @yandexx Filter a log file by matching multiple regular expressions
- @alisha17 Serialize records to CSV
- @Ophirr33 added verify email and extract login example
- @Phaiax Add Replace text with named capture groups example. fixes #243
- @Phaiax Add Extract unique Hashtag example. Fixes #242
- @Ophirr33 File Loop app example
- @alisha17 Handle invalid CSV data with Serde
- @alisha17 Read csv records with different delimeter
- @tshepang improved readability and fixed typos
-
@jaemk update
stdbadge version - @budziq fixed links and CI auto-deploy after move to rust-lang-nursery
5 Likes
Hi can anyone with rust-lang-nursery rights enable appveyor for rust-cookbook? https://ci.appveyor.com/rust-lang-nursery/rust-cookbook
I’d like to add windows ci but being collaborator but not organization member makes me short on foo here
Please note that enabling under rust-lang-libs instead of nursery domain will not work ok due to weird appveyor permissions making me unable to start builds (We’ve already tried that with Alex earlier this week 
)
EDIT:
Already done thanks to @alexcrichton! 
Rayon is coming up for the meeting next week – are we as authors supposed to prepare anything? I thought that some external person is supposed to do a review beforehand, but I haven’t seen that.
Gah oops, done now!
2 Likes