Martmists-GH / Martmists-GH/ndarray.simd
Consider FFM instead of JNI on JVM
Open
Nobody has claimed this yet.
enhancement
good first issue
help wanted
- Dominant language
- Kotlin
- Stars
- 12
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This would still need a thin layer to handle offsets, but may be worth looking into.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the current JNI integration and comparing it with JVM Foreign Function and Memory API support, including the required offset-handling layer. Done means establishing whether FFM is viable and documenting the resulting implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100