Skip to content

docs: fix example require path in strided/base/reinterpret-int64 - #14719

Merged
kgryte merged 1 commit into
developfrom
philipp/fix-commit-review-2026-08-27
Aug 27, 2026
Merged

kgryte merged 1 commit into
developfrom
philipp/fix-commit-review-2026-08-27

Conversation

@Planeshifter

Copy link
Copy Markdown
Member

Description

What is the purpose of this pull request?

This pull request:

  • provides follow-up fixes for commits merged to develop between 2026-08-26 20:29 PDT (09fa89a) and 2026-08-27 04:05 PDT (607bbc6). All 41 commits in the window were reviewed for typos, bugs, and style guide violations. One issue survived validation:

strided/base/reinterpret-int64

  • Fix incorrect require( '@stdlib/array/complex128' ) in the TS declaration's JSDoc example (92db74a); every other file in the package uses @stdlib/array/int64, and this was just copy-pasted from reinterpret-uint64's .d.ts. Now requires @stdlib/array/int64.

Related Issues

Does this pull request have any related issues?

No.

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.

Validation. The commit window was checked for: stdlib style guide compliance (docs/style-guides, changed code compared against established sibling packages), objective bugs in the introduced code (logic, indexing, numerical values in doc examples, security), and typos in user-visible text. Deliberately excluded: subjective suggestions, anything requiring interpretation, and anything whose fix would touch code outside the window's diff — notably, reinterpret-uint64/docs/types/index.d.ts carries the same wrong require on a pre-existing (unchanged) line, left for a separate PR.

Checklist

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

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. 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.".

This PR was produced by a scheduled Claude Code review of the last 24 hours of commits merged to develop; findings were cross-validated by multiple independent review passes before being applied.


Generated by Claude Code

@stdlib-bot

Copy link
Copy Markdown
Contributor

Coverage Report

Package Statements Branches Functions Lines
strided/base/reinterpret-int64 $\\color{green}99/99$
$\\color{green}+100.00\\%$
$\\color{green}3/3$
$\\color{green}+100.00\\%$
$\\color{green}1/1$
$\\color{green}+100.00\\%$
$\\color{green}99/99$
$\\color{green}+100.00\\%$

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

@kgryte kgryte added the Documentation Improvements, additions, or changes to documentation. label Aug 27, 2026
@kgryte
kgryte marked this pull request as ready for review August 27, 2026 23:57
@kgryte
kgryte requested a review from a team August 27, 2026 23:57
@stdlib-bot stdlib-bot added the Needs Review A pull request which needs code review. label Aug 27, 2026
@kgryte
kgryte merged commit c0a29a3 into develop Aug 27, 2026
50 checks passed
@stdlib-bot stdlib-bot removed the Needs Review A pull request which needs code review. label Aug 27, 2026
@kgryte
kgryte deleted the philipp/fix-commit-review-2026-08-27 branch August 27, 2026 23:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Documentation Improvements, additions, or changes to documentation.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants