Remove runtime APIs deprecated for ReScript 13

[cknitt]

Summary

• Remove runtime APIs explicitly deprecated for removal in ReScript 13:
  • the Char module
  • unsafe Obj operations
  • legacy Pervasives helpers
  • Array.unsafe_get
• Migrate runtime, Belt, documentation examples, and tests to supported APIs.
• Regenerate runtime JavaScript and artifact manifests.

Obj.magic and Array.getUnsafe remain available.

Motivation

These APIs were scheduled for removal in ReScript 13. Removing them now completes that deprecation cycle and updates internal callers to the supported standard-library equivalents.

Validation

• make test
• make lib
• yarn workspace @tests/belt rescript build
• git diff --check

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.76%. Comparing base (45f7582) to head (1ae8b42).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8564      +/-   ##
==========================================
- Coverage   75.79%   75.76%   -0.03%     
==========================================
  Files         476      476              
  Lines       62680    62680              
==========================================
- Hits        47506    47489      -17     
- Misses      15174    15191      +17     

see 12 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pkg-pr-new]

Open in StackBlitz

rescript

npm i https://pkg.pr.new/rescript-lang/rescript@8564

@rescript/belt

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/belt@8564

@rescript/darwin-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-arm64@8564

@rescript/darwin-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/darwin-x64@8564

@rescript/linux-arm64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-arm64@8564

@rescript/linux-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/linux-x64@8564

@rescript/runtime

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/runtime@8564

@rescript/win32-x64

npm i https://pkg.pr.new/rescript-lang/rescript/@rescript/win32-x64@8564

commit: 1ae8b42

[tsnobip]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: 1ae8b42656

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[tsnobip]

I only have one comment, except from that it looks good to me!

[tsnobip]

why are we losing the | 0 part here?

[cknitt]

The source previously used lor(lsl(size, 10), 0). Since x | 0 is a no-op here and JavaScript's << already coerces its operands and returns a signed 32-bit integer, size << 10 has the same behavior. So losing the trailing | 0 is intentional.

[tsnobip]

why did we did not replace lor here?

Suggested change

	s.contents = hash_mix_int(s.contents, Int.shiftLeft(size, 10)) /* tag */
	s.contents = hash_mix_int(s.contents, Int.bitwiseOr(Int.shiftLeft(size, 10), 0)) /* tag */

[cknitt]

We could preserve the mechanical translation with Int.bitwiseOr(Int.shiftLeft(size, 10), 0), but the bitwiseOr(..., 0) is redundant: Int.shiftLeft already has the required int32 semantics. I simplified it to Int.shiftLeft(size, 10) rather than retaining the no-op.