Jacob Pratt

I don't have time to look through the RFC this moment, but I'm hoping this will be forward compatible with intra-package libraries? I described my thoughts a bit [in this...

Fwiw the "single piece of software" will be wholly covered by the proposal I linked to earlier. I'm hoping to provide additional clarity on this point soon.

@matklad Would a PR implementing this be accepted? I'm also interested in implementing `impl AsRef for Lazy where T: AsRef` for similar reasons.

Yeah, that's definitely true. Perhaps waiting for this to get into std would be best. I just ran into `AsRef` because I was iterating over a reference, which led to...

(Un?)fortunately I already rewrote that bit of code to avoid it. One of the dereferences was due to the iterator, the second was because I was iterating over references (to...

The reason `Iterator::intersperse` hasn't had any progress towards re-stabilization appears to be _because_ this PR hasn't been merged.

Couldn't a `targets` input be provided, explicitly overriding `targef`? That would be back-compatible. Alternatively, it could be additive.

Having a `toolchains` option similar to `targets` would be useful for some use cases as well. The advantage being the ability to auto-install targets when you know multiple toolchains will...

For what it's worth, I just tried using action/cache@v1 in combination with overriding permissions (to avoid errors), and found minimal difference in speed. It seems the network is the restricting...

@tim-mc @littledan @rricard Any updates on the progress?