Jacob Finkelman
Jacob Finkelman
Let's focus on making the change here. We can deal with updating the guide once the code has been changed.
I don't quite see why the URL situation requires crashing out, but I may not understand all the architectural decisions involved here. One solution that is already available is returning...
The more I thought about this idea the more I love it. These patterns should all be identifiable in a error tree.
Thank you for giving this a try! I look forward to reading over your elm example! It is related to https://github.com/pubgrub-rs/advanced_dependency_providers/issues/6. The first problem is that we don't fit well...
CC #138
Thank you for creating the issue, it will give us a place to remember to continue the conversation. I look forward to learning from your deep experience, and the performance...
That makes a lot of sense. I think the existing API fits in your model as the synchronous resolution algorithm, which is called inside some wrapper that does the asynchronous...
That is 100% possible with wrappers around PubGrub! I absolutely need to document as an example (and in the book) how to put the pieces together.
For some context #36 especially [this comment](https://github.com/pubgrub-rs/pubgrub/issues/36#issuecomment-709400796) and the PR #55. Our surface level interface does not have a way to express this. It can only say "A depends on...
Yes we will have to change the return type of `get_dependencies` from `Result`. We could add in Enum for whether each dependency is `required` or `constrained` (wordsmithing required), something like...