feat: add number/int64/ctor

[impawstarlight]

Resolves none.

Description

What is the purpose of this pull request?

This pull request:

• Adds support for 64-bit signed integers by adding number/int64/ctor

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.

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

N/A.

---

@stdlib-js/reviewers

[stdlib-bot]

Hello! Thank you for your contribution to stdlib.

We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:

1. Please read our contributing guidelines.

2. Update your pull request description to include this checked box:

   - [x] Read, understood, and followed the [contributing guidelines](https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md)

This acknowledgment confirms that you've read the guidelines, which include:

• The developer's certificate of origin
• Your agreement to license your contributions under the project's terms

We can't review or accept contributions without this acknowledgment.

Thank you for your understanding and cooperation. We look forward to reviewing your contribution!

[impawstarlight]

/stdlib update-copyright-years

[stdlib-bot]

/stdlib update-copyright-years

@impawstarlight, the slash command failed to complete. Please check the workflow logs for details.

View workflow run

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
number/int64/ctor	$\\color{red}603/685$ $\\color{red}-0.15\\%$	$\\color{red}51/55$ $\\color{green}+0.00\\%$	$\\color{red}9/11$ $\\color{green}+0.00\\%$	$\\color{red}603/685$ $\\color{red}-0.15\\%$

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

[impawstarlight]

/stdlib update-copyright-years

[stdlib-bot]

/stdlib update-copyright-years

@impawstarlight, the slash command failed to complete. Please check the workflow logs for details.

View workflow run

[impawstarlight]

/stdlib update-copyright-years

[stdlib-bot]

/stdlib update-copyright-years

@impawstarlight, the slash command failed to complete. Please check the workflow logs for details.

View workflow run

[kgryte]

@impawstarlight Is there a reason you need to run the update-copyright-years slash command? This should be a simple search-and-replace in local dev. E.g., what I like to do locally is to open an editor window for just the package I am working on and then do a global find-and-replace using 20(\d{2}) as the regexp to match with 2026 as the replacement value. This works well for me, and I never rely on CI for doing this. We only added the update-copyright-years command as a way for reviewers to fixup copyright years without having to actually pull down a PR's changes.

[kgryte]

Suggested change

	bench( format( '%s::from', pkg ), function benchmark( b ) {
	bench( format( '%s:from', pkg ), function benchmark( b ) {

[impawstarlight]

So, single colon for actual method name and double colon for conceptual title?

[kgryte]

Given that this is the same code as in Uint64, maybe as a follow-up PR we should create a separate package which we can then use in both constructor packages. E.g., number/uint64/base/words2string or similar.

[impawstarlight]

Yeah, that's the plan.

[kgryte]

Overall, this is looking good. Main quibble is in tightening up the tests. This also applies to number/uint64/ctor which can be addressed in a follow-up PR.

[impawstarlight]

@impawstarlight Is there a reason you need to run the update-copyright-years slash command? This should be a simple search-and-replace in local dev. E.g., what I like to do locally is to open an editor window for just the package I am working on and then do a global find-and-replace using 20(\d{2}) as the regexp to match with 2026 as the replacement value. This works well for me, and I never rely on CI for doing this. We only added the update-copyright-years command as a way for reviewers to fixup copyright years without having to actually pull down a PR's changes.

Ah I see. I used do it locally in the past but I somehow got the wrong idea that maybe using the slash command is better from our past meetings and other people's usage. I'll keep it in mind. 😞

[impawstarlight]

This is from uint64/ctor:

@param {(NonNegativeInteger|bigint)} value - integer value

Is there a just Integer counterpart that encompasses both positives and negatives which can be used in int64/ctor jsdoc comments? I tried Integer but that results in lint error. Currently it's just number which is okay I guess but wanna know the situation. And IIRC, integer and uinteger is restricted to 32-bit values, right?