What does native_functions.yaml have to do with the TorchScript compiler? What multiple use cases is native_functions.yaml trying to serve? What's up with the JIT schema type system? Why isn't it just Python types? What the heck is the (a!) thingy inside the schema? Why is it important that I actually annotate all of my functions accurately with this information? Why is my seemingly BC change to native_functions.yaml actually breaking people's code? Do I have to understand the entire compiler to understand how to work with these systems?Further reading.<ul><li>native_functions.yaml README <a href="https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/README.md">https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/native/README.md</a></li><li>Tracking issue for serializing default arguments <a href="https://github.com/pytorch/pytorch/issues/54613">https://github.com/pytorch/pytorch/issues/54613</a></li><li>Test for BC breaking changes in native_functions.yaml <a href="https://github.com/pytorch/pytorch/blob/master/test/backward_compatibility/check_backward_compatibility.py">https://github.com/pytorch/pytorch/blob/master/test/backward_compatibility/check_backward_compatibility.py</a></li></ul>

TensorIterator

The PyTorch Developer Podcast is a place for the PyTorch dev team to do bite sized (10-20 min) topics about all sorts of internal development topics in PyTorch.