I know it has to be converted to a proc either way...but by passing it along as `&proc`, rather than just `proc`, my understanding is that ruby calls `to_proc` on it, and then potentially round-trips it through the proc reification process when it is re-captured in `Procsy#initialize` as `&proc`.  Or once ruby has converted it to a proc once, is there no more cost to roundtripping it through the `&` syntax anymore?  Regardless, the goal in `Procsy` is to have a reference to a `Proc` object and you have one...so you can just pass it along as a normal arg at this point.  I'm unsure if it'll make a difference, honestly, but my intuition is that passing it along as normal arg _might_ be faster and I can't imagine it being slower.