Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[RFC]: add C implementations for `blas/ext/base/ndarray` packages

Abierto
  • ¿Algo no está bien?
#14,819 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Arjan-P ya está trabajando en esto.

Desde el 2/9/2026.

  • #14827 de @Nehant14 — cerrado sin fusionar
  • #14906 de @Arjan-P — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c, javascript
Área
backend, data

Línea de trabajo

Elige un paquete no reclamado en blas/ext/base/ndarray y compara primero su implementación de JavaScript con la PR de referencia correspondiente. Revisa los archivos src/, include/, manifest.json y binding.gyp del paquete, y después usa el rastreador de PR para comentar en este issue antes de comenzar. Se considera terminado cuando el paquete tiene la implementación nativa correspondiente en C y una PR enlazada.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Accepted C Feature Native Addons RFC Tracking Issue

Purpose

This issue tracks the initiative to add native C implementations for typed ndarray APIs in blas/ext/base/ndarray. It serves as a central reference point for contributors so that work can be coordinated, PRs can be linked back here, and duplicate effort can be avoided.

Summary

In blas/ext/base/ndarray, if a typed ndarray API is missing a native C implementation, it is fair game to add one. This issue serves as a general tracking reference for this ongoing initiative.

Candidates for C implementations typically include packages handling the following data types (indicated by their prefixes):

  • d (double-precision)
  • s (single-precision)
  • c (complex single-precision)
  • z (complex double-precision)

Since new strided APIs are constantly being added to blas/ext/base, this is intentionally kept as a generalized issue rather than an enumerated checklist, which would become outdated quickly.

What to Do

If you find a package under blas/ext/base/ndarray that has a JavaScript implementation but is missing a native C addon (src/, include/, manifest.json, binding.gyp, etc.), you may go ahead and add the C implementation.

Reference Library

To help contributors understand exactly what is required when adding a native C implementation, we have compiled a "Reference Library" of merged PRs. Please refer to the PR that best matches the type of package you are working on:

PR Title Convention

When opening a pull request for this work, please use the following title format so others can easily search GitHub and avoid duplicate PRs:

feat: add C implementation for `blas/ext/base/ndarray/<package-name>`

You are Advised

  • Before starting, please leave a comment on this issue mentioning which package you are working on (e.g., "I am working on dsum"). This helps avoid two contributors working on the same package simultaneously.
  • Reference this issue in your PR description if you are adding a C implementation for any blas/ext/base/ndarray package. This helps reviewers understand the context and track progress against this initiative.
  • Check the PR tracker before starting to make sure there is no existing open PR for the same package.
Related Issues

None.

Questions

No.

Other

No.

Checklist
  • I have read and understood the Code of Conduct.
  • Searched for existing issues and pull requests.
  • The issue name begins with RFC:.
Lenguaje dominante
JavaScript
Estrellas
6k
Forks
1.3k
Merge medio
1 d 10 h
PR fusionados (30 d)
568

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stdlib-js/stdlib

Todos los issues de stdlib-js/stdlib

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.