Stephen Celis
Stephen Celis
It's following the specification of the dependent gem. You should be able to bypass this with --cached.
Wouldn't it make more sense to use a shared cache directory? Issue #156 brings this up.
Haha, not a bad idea and something I'd never really stopped to think about. Any ideas?
I'll mull it over. On the other hand `app` is pretty good as the gem name itself... It doesn't get much simpler than `gem 'app'` and `gem install app`.
@runspired I think readers would be interested in more information regarding what was factually deficient (and why) before this change could possibly be accepted.
@lorentey Feel free to close this or convert to a discussion! And thanks for the suggestion of fixing our performance issue. We believe we've done so here: https://github.com/pointfreeco/swift-identified-collections/pull/16
> Re [pointfreeco/swift-identified-collections#16](https://github.com/pointfreeco/swift-identified-collections/pull/16): I suspect the move operation will need to use a stable partition, or the order of elements will be scrambled. 🤔 Ah thanks! I've instead cribbed the...
It might not even have to be a breaking change immediately. We could add the protocol extension layer and call the module functions from there. The question is if Swift...
If no one else wants to noodle on this, I can take a stab this weekend :smile:
Did a quick look at this and it doesn't look like `var to` and `func to()` can live in harmony :disappointed: I see two paths forward… 1. The backwards-compatible: ```...