Skip to content

fix: use the String API that survives v4.35.0-rc3 - #10

Merged
kim-em merged 1 commit into
mainfrom
fix/string-api-v4.35
Sep 28, 2026
Merged

kim-em merged 1 commit into
mainfrom
fix/string-api-v4.35

Conversation

@kim-em

@kim-em kim-em commented Sep 28, 2026

Copy link
Copy Markdown
Collaborator

This PR moves four call sites off String.trim and String.dropRight, which v4.35.0-rc3 removes.

Core/Generate.lean stops elaborating at that toolchain, and because a Lake dependency is built with the root project's toolchain, that breaks any downstream project moving to v4.35.0-rc3 even though this package pins v4.33.0 itself. lean-eval hits it: its lean-eval executable fails to build with four Invalid field errors from this file.

The replacements are trimAscii and dropEnd. Both return a String.Slice rather than a String, so each call gains the .toString that line 1848 of this same file was already using for trimAsciiEnd.

No toolchain change is needed here. The replacements have existed since long before v4.33.0 and the old names were merely deprecated until rc3 removed them, so lake build is clean both on this package's own v4.33.0 and on v4.35.0-rc3.

🤖 Prepared with Claude Code

`String.trim` and `String.dropRight` are removed in v4.35.0-rc3, so
`Core/Generate.lean` no longer elaborates there, which in turn breaks any
downstream project that builds this package at that toolchain.

Move the four sites to `trimAscii` and `dropEnd`. Both return a
`String.Slice`, so each call gains the `.toString` that line 1848 of the same
file was already using for `trimAsciiEnd`.

The replacements have existed since well before v4.33.0 -- the old names were
merely deprecated until rc3 removed them -- so this needs no toolchain change
here: `lake build` is clean on this package's own v4.33.0 and on v4.35.0-rc3.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kim-em
kim-em merged commit a61cd80 into main Sep 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant