microsoft / microsoft/yardl

use / support for python / numpy array api

Open
#107 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
C++
Stars
35
Forks
14
Avg merge
5d 17h
Merged PRs (30d)
1

Description

Dear Yardl developers,

would it be (in principle) possible to use numpy.array_api instead of numpy as array backend for the generated python code?
Note that numpy.array_api is a reference implementation of the array API standard.

By doing so, Yardl would be compliant with the python array api and as such more agnostic to the specific array backend which would potentially allow using other compliant array backends (e.g. cupy or pytorch) in the future.

Georg

PS: @johnstairs @hansenms thanks for the support of the 1st ETSI Hackathon

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the generated Python code and the places where it depends on numpy. Read the numpy.array_api and Array API standard references linked in the issue, then determine the scope needed for generated code to support that interface and other compliant backends. Done should mean the requested array API support is implemented and verified against the generated Python output.

Written by the indexing model from the issue text.

Assessment

Tech stack
numpy, python
Domain
data, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.