Albert Steppi
Albert Steppi
I've updated this to include three tables for CPU, GPU, and JIT as suggested by @rgommers. I've also incorporated the suggestions to reduce the number of characters per cell. It's...
> It doesn't have to be in this PR but we need a way of marking functions that won't be converted. For example the datasets sub-module displays 0% coverage however...
I'm thinking that it may be best to use the `xp_capabilities` decorator to give the source of truth for which functions are out of scope. I'm curious about the desired...
Declaring things out of scope with `xp_capabilities` is working now. For proof of concept, I've added the decorator to the relevant functions in `constants`. I used the below symbol for...
OK, using "N/A" looks much better. 
docs link https://output.circle-artifacts.com/output/job/91a0013e-5321-4ccd-adee-e1ec1e2a2d39/artifacts/0/html/index.html
> Hey @steppi, can I help move this along? Yes, there are things you could do. We need to make `xp_capabilities` use universal in SciPy before this goes in. I've...
> It might be useful to merge this and work on adding `xp_capabilities` incrementally` as thing like the out of scope marker added in this pr would be quite useful...
I'm OK with merging this now if anyone wants to push the button on it.
> Also the coverage of sub-modules doesn't seem complete e.g. there is `spatial.distance` but no `spatial.transform` and a few other cases Currently the tables only include functions and other callables...