-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implemented sinc in the backend #4436
Conversation
Hi, Could you also link the issue this relates to. This is so that it's easier for us to track what's being done. Thanks |
@Unevilicorn thank you for the review, I will fix the tests by EOD. sinc is a part of the functional API and is referenced in the Frontend TODO lists #12 , #1525 and #3612 |
I would actually recommend doing this compositionally then, since this function isn't too complex to compose, you can see it's behaviour from pytorch docs. I'll take another look, and check if this should be added to the list 👍 |
I understand. So instead of adding any backend functions, I should implement sinc compositionally to only the frontend files of Numpy and Torch, as mentioned in the frontend todo tasks, right? |
Yeah, that's the simplest way to go about it, just implementing them compositionally in the frontend for your framework. However it does feel like it could be added as an extension, I'll let you know when I find out if this should be added or not. |
Alright then! Closing this PR for now, and will work on the frontend as you suggested. Let me know if there is a need for it in the backend, I'd love to get back on it 🙌🏻 Thanks alot for your help!! |
Hi @pj-mathematician, |
@Unevilicorn , I have opened #4462 to work on this. Thank you for the clarification |
Can you review and please list the additions/deletions I should incorporate?
And I will also need help with the doc string for ivy/elementwise.py
Thanks