We will want to add in vendor-specific names (like openblas_get_num_threads()) which should be harmless, but we definitely want to write some generic APIs over the vendor-specific stuff so that we can, for instance, get/set the number of threads no matter whether we're using MKL or OpenBLAS, as right now it's difficult to know precisely which one we're using and you don't want to try and call the wrong one.
If we can get a list of the vendor-specific APIs that we might want, we can think about the best way to wrap them.
Quoting @staticfloat from #2:
We will want to add in vendor-specific names (like openblas_get_num_threads()) which should be harmless, but we definitely want to write some generic APIs over the vendor-specific stuff so that we can, for instance, get/set the number of threads no matter whether we're using MKL or OpenBLAS, as right now it's difficult to know precisely which one we're using and you don't want to try and call the wrong one.
If we can get a list of the vendor-specific APIs that we might want, we can think about the best way to wrap them.