jyn

FWIW https://docs.rs/std::fs redirects to https://doc.rust-lang.org/stable/std/?search=fs

@Mark-Simulacrum https://github.com/rust-lang/docs.rs/issues/1757 has a detailed rationale. The tldr is that crates in workspaces often have very large dependency trees that are the same between all the crates in the workspace....

> @jyn514 could you explain more? You mean making it readonly when it's in the cache? Or when it's restored for the build? When it's restored. The idea is to...

> So the build will ever only create files? And never update or delete them? > Setting them to readonly should be possible then, but that would have to be...

I haven't looked into this in detail since my last review, but i want to say - having a way to turn this off in prod without needing to revert...

I am dubious how much sccache will actually help in practice. I would like to see benchmarks on how much it helps with large workspace if you're planning to *only*...

That said landing sccache seems fine as a first step as long as you don't close out the tracking issue.

I would love to have this - right now `changelog` makes a separate entry for each commit, but docs.rs doesn't have a clean commit history, the unit of change is...

Also, I'd like to say how much I love the bug report panic handler :) It gives all the info for the bug report so I can copy paste it...

This seems to have been fixed: https://github.com/vavrusa/memcache-async/blob/b72b6b82229e901734ca4f96f1438afca6b81c68/Cargo.toml#L10