Martmists-GH/ndarray.simd

Consider FFM instead of JNI on JVM

Open

#4 opened on Dec 5, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Kotlin (0 forks)auto 404
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (12 stars)
PR merge metrics
 (PR metrics pending)

Description

This would still need a thin layer to handle offsets, but may be worth looking into.

Contributor guide

Research direction
Explore the Foreign Function & Memory (FFM) API and compare it with JNI for native array operations in Kotlin on JVM. Investigate performance implications, implementation complexity, and how to integrate with the existing NDArray codebase.
Tech stack
kotlinjava
Domain
backendapi
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
KotlinJavaJNI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50