Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Port all functions from ArrayFire 3.4

Open
#7 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, r
Domain
data

Research direction

Review the porting checklist and compare the existing src/foo.cpp and R/foo.R pairs for the completed headers. Then work through the remaining headers, adding test/simple_foo.R tests where possible. Done means the listed functions are ported, with the explicitly excluded C++-only headers left out.

Written by the indexing model from the issue text.

Description

Each header "foo" file should have the following:

  • src/foo.cpp
  • R/foo.R

Also add tests if possible, though they are not necessary

  • test/simple_foo.R
  • algorithm
  • arith
  • array
  • blas
  • data
  • defines (library.py)
  • device
  • features
  • graphics
  • image
  • index
  • lapack
  • signal
  • statistics
  • util
  • version (merge with util)
  • vision

C++ only headers that are not being ported

  • exception.h (ported the necessary C function to util.py)
  • complex.h
  • dim4.hpp
  • gfor (are there any necessary bits??)
  • constants
Dominant language
R
Stars
22
Forks
5
PR merge metrics
No merged PRs in 30d

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.

More from arrayfire/arrayfire-r

All issues in arrayfire/arrayfire-r

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.