NumPy API Coverage & Support
See the supported surface. Find the next gap.
Explore the NumPy catalog across functions, modules, and object members, with NumSharp equivalents, known limitations, C# overloads checked against NumPy's signatures, and the committed NumPy-oracle contracts that prove each API's parity. The page is generated from the same artifact published by CI.
Summaries, cards, and the explorer follow the selected scope. Availability is available ÷ NumPy APIs in that scope; supporting types, constants, modules, and NumSharp-only APIs do not enter this percentage. “Available” means an exact public member or a reviewed alias exists and is not marked partial/unsupported. The headline comparison also excludes extended APIs. Two kinds of NumPy API are listed but not counted in any percentage or gap count, because neither describes something NumSharp could implement: a call NumPy itself refuses (a unary ufunc's reduce, del a[i], ordering comparisons of ndarray.flags), and a member that a class NumSharp has no type for (memmap, recarray, record, MaskedRecords) inherits unchanged from a class whose own rows already count it; that class shows its gap through its class row and its own members. A NumPy scalar is a read-only 0-d NDArray in NumSharp, so the scalar types' members are credited against NDArray. API presence is not a blanket edge-case, dtype, layout, or signature parity claim. Oracle-verified is that claim's evidence: committed output of the pinned NumPy release (named at the top of the page; the differential-fuzz corpus plus the .npy, flags and layout oracles, and the string oracle's numpy.strings and numpy.char calls) that CI replays against NumSharp, bit-exact or a documented divergence, resolved to the API directly or through an identity or reviewed delegation alias; a corpus key the replay runs through a C# operator (a + b, a == b) also verifies that operator's ndarray protocol. NumPy-identical signature is a separate check: one C# overload with exactly NumPy's parameters (names, positions, defaults) under NumPy's name, and NumPy-style calls of it compile. It comes from the API diff gap map (tools/api-parameter-parity), which compares every C# spelling (functions, members, constructors, extension methods, NDArray<T>) and compiles NumPy-style calls at C# 12 and C# 14. Marks of a differing call: M a NumPy parameter no overload offers, X a parameter NumPy does not have, O more than one overload, T a dtype taken as NPTypeCode / Type or picked by a generic type argument, B a NumPy-style call that does not compile, L null refused where NumPy's default is None, Q an integer sequence refused where NumPy allows one, N credited through another name.
Support mix
Select a segment to send that status into the explorer. Hover, focus, or click for its API breakdown.
Surface scoreboard
Every module and object surface in the selected scope. Select a card to explore its APIs.
Capability map
Categories are assigned deterministically by the artifact generator. Select one to investigate it.
API explorer
Search NumPy names, NumSharp targets, signatures, categories, and review notes.