[gunjjoshi]

---

type: pre_commit_static_analysis_report
description: Results of running static analysis checks when committing changes. report:

• task: lint_filenames status: passed
• task: lint_editorconfig status: passed
• task: lint_markdown_pkg_readmes status: passed
• task: lint_markdown_docs status: na
• task: lint_markdown status: na
• task: lint_package_json status: passed
• task: lint_repl_help status: passed
• task: lint_javascript_src status: passed
• task: lint_javascript_cli status: na
• task: lint_javascript_examples status: passed
• task: lint_javascript_tests status: passed
• task: lint_javascript_benchmarks status: passed
• task: lint_python status: na
• task: lint_r status: na
• task: lint_c_src status: na
• task: lint_c_examples status: na
• task: lint_c_benchmarks status: na
• task: lint_c_tests_fixtures status: na
• task: lint_shell status: na
• task: lint_typescript_declarations status: passed
• task: lint_typescript_tests status: passed
• task: lint_license_headers status: passed ---

Resolves a part of stdlib-js/metr-issue-tracker#1385.

Description

What is the purpose of this pull request?

This pull request:

• adds fft/fftpack/rffti, which will be helpful for feat: add fft/rfftf #16089.

Related Issues

Does this pull request have any related issues?

This pull request has the following related issues:

• [RFC]: add fft/rfftf metr-issue-tracker#1385.

Reference Packages

Did the content of this pull request follow one or more existing packages? Answering is optional.

This pull request followed these packages:

• blas/ext/one-to.

What carried over from the reference(s)?

• test structure, docs, benchmarks, and some part of the implementation.

What differed, or what did you have to work out yourself?

• The logic of having a workspace array differed.

Questions

Any questions for reviewers of this pull request?

No.

Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

• Read, understood, and followed the contributing guidelines.

AI Assistance

When authoring the changes proposed in this PR, did you use any kind of AI assistance?

• Yes
• No

If you answered "yes" above, how did you use AI assistance?

• Code generation (e.g., when writing an implementation or fixing a bug)
• Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

If you answered "yes" to using AI assistance, please provide a short disclosure indicating how you used AI assistance. This helps reviewers determine how much scrutiny to apply when reviewing your contribution. Example disclosures: "This PR was written primarily by Claude Code." or "I consulted ChatGPT to understand the codebase, but the proposed changes were fully authored manually by myself.".

Used Claude code to help with implementation and research, and then did a manual review.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
fft/fftpack/rffti	$\\color{green}421/421$ $\\color{green}+100.00\\%$	$\\color{green}24/24$ $\\color{green}+100.00\\%$	$\\color{green}3/3$ $\\color{green}+100.00\\%$	$\\color{green}421/421$ $\\color{green}+100.00\\%$

The above coverage report was generated for the changes in this PR.

[kgryte]

I suggest actually testing the workspace contents here.

[kgryte]

I think you also should test for a "generic" output array.

[kgryte]

I suggest testing for the values here.

[kgryte]

As discussed, let's move this package to fft/fftpack/rffti, as this API is FFTPACK-specific.

[gunjjoshi]

@kgryte I have now updated the tests to check for the values inside the workspace array, for float64, float32 and generic ndarrays, similar to that in https://github.com/stdlib-js/stdlib/blob/develop/lib/node_modules/%40stdlib/fft/base/fftpack/ndarray/float64/rffti/test/test.js#L65.

[gunjjoshi]

As discussed, let's move this package to fft/fftpack/rffti, as this API is FFTPACK-specific.

Done.