Open fschlimb opened 3 years ago
Thanks a lot for this list @fschlimb!
bitwise_invert
, bitwise_left_shift
and bitwise_right_shift
are implemented as ht.invert
, ht.left_shift
and ht.right_shift
following the NumPy API reference.
hello @ClaudiaComito , I would like to work on this issue as a part of gsoc. It would be great If you could guide me how can I start. I am aware of numpy but not much aware of parallel computing. I found project here:https://docs.google.com/document/d/1OKUf_n_whN0M20c__jj8R5jyGABPYYxmdBfyzto4OZk/edit
This is still work-in-progress and being tracked in #1022.
Reviewed within #1109
Check out https://github.com/data-apis/array-api/issues/462 for tracking and potentially signalling array API compliance, although it doesn't look like the workflow is final.
Re: how/whom to report compliance to, we could be contributing Heat JSON data to the array-api-comparison repository.
If I understand correctly, the JSON data are created when running the array-api-tests with the -json-report
option, see example workflow here.
I managed to clone the repo and compile their tools, the result looks something like this:
What do you think @mtar @mrfh92 ?
That repository has nothing to do with compliance. It helps comparing the names of equivalent functions in existing libraries.
A consortium is defining an Array API: https://data-apis.org/array-api/latest/index.html
It seems desirable for HeAT to be as compliant as possible.
The following features are missing in HeAT (others are probably incomplete):
The following features are missing in the array itself (others are probably incomplete):