io

I'm opening this issue prepared to be declared blind and pointed at the relevant bit of documentation, but I've looked far and wide, and it's definitely not in this repo, not in a form that a grep can find.

What should happen if deliver_cancel raises an exception? In the current implementation, the shielded cancel scope will prevent it from propagating until the process exits, which might take a while if the crash occurred before signaling the process in any way. Maybe on exception from a user-specified deliver_cancel we should call the default deliver_cancel to kill the process? Or just kill() since

🚀 The feature

Cache PitchShift Resample kernel to improve speed of this transform on second usage.

Motivation, pitch

In porting some augmentation code from librosa to torchaudio, I noticed that PitchShift() and Resample() are slower than librosa in CPU.

In the case of transforms.Resample(), this changes on second run as the kernel is cached. But PitchShift does no such cach