Low Level Non Allocating API

Open
  • Is something wrong?
#125 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
julia
Domain
backend-api-design, performance

Research direction

Start by locating the FFT functions and the fft! path involved when using FFTW.jl. Reproduce the shown @allocated check with a ComplexF64 vector, then define the workspace API and verify that the non-allocating variant performs no allocations, including the static-binary use case.

Written by the indexing model from the issue text.

Description

It would be great to have non allocating variants of the FFT functions.

vA = rand(ComplexF64, 1000);
@allocated fft!(vA)

I get some allocations (Using FFTW.jl).
It would be great to have a low level API which has no allocations at all.
It might require an auxiliary function to generate the needed workspace.

It will be appreciated in the context of static binaries generated by Julia.

Dominant language
Julia
Stars
135
Forks
40
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 JuliaMath/AbstractFFTs.jl

All issues in JuliaMath/AbstractFFTs.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.