maitake-sync's waitmap::Wait future has an enqueue method that
does the same thing as the subscribe methods on WaitCell and
WaitQueue...but has a different name. I think this might be due to
enqueue being added earlier or something, or maybe we just weren't
paying attention. Regardless, I figured it was nicer to use the same
name for the method that does the same thing on these different types.
This commit renames the waitmap::Wait::enqueue method to subscribe,
and the future it returns from EnqueueWait to Subscribe, analogously
to WaitQueue and WaitCell. I've left a deprecated type alias and a
deprecated function alias in place, so this isn't a breaking change:
users who reference Wait::enqueue or EnqueueWait will still be able
to compile their code, but they'll get a warning.
cc @jamesmunns, since I believe you added this API?
maitake-sync'swaitmap::Waitfuture has anenqueuemethod that does the same thing as thesubscribemethods onWaitCellandWaitQueue...but has a different name. I think this might be due toenqueuebeing added earlier or something, or maybe we just weren't paying attention. Regardless, I figured it was nicer to use the same name for the method that does the same thing on these different types.This commit renames the
waitmap::Wait::enqueuemethod tosubscribe, and the future it returns fromEnqueueWaittoSubscribe, analogously toWaitQueueandWaitCell. I've left a deprecated type alias and a deprecated function alias in place, so this isn't a breaking change: users who referenceWait::enqueueorEnqueueWaitwill still be able to compile their code, but they'll get a warning.cc @jamesmunns, since I believe you added this API?