@nikomatsakis you mentioned before you wanted polonius to basically compute all loans in scope for all origins, and I wondered about that, did we absolutely need all loans for a reason that I didn't know yet (I was wondering whether that would be needed for diagnostics for example). I was looking for ways to avoid materializing and propagating loans if possible, or at least delaying them or computing them lazily for as long as we could until we knew for sure that there was an error. (I do realize that right now propagating loans is how we detect errors, and would require an alternative way of doing so)
@lqd I don't recall expressing an opinion about this ...
off the top of my head I can't see why we need to compute all loans in scope for all origins
and if we did need it for diagnostics, which I don't think we do, I imagine we could compute it on demand
I mean we currently eagerly compute all loans contained at every point in the cfg (with some possible filtering wrt "all origins") but couldn't see a reason that we absolutely had to and wanted to make sure I wasn't missing something :)
nope, I think I always expected us to use feedback to limit that
nice, thank you :)