TypeScript: read vtable entries as uint16#8435
Merged
bjornharrtell merged 3 commits intogoogle:masterfrom Nov 27, 2025
Merged
Conversation
Contributor
|
This pull request is stale because it has been open 6 months with no activity. Please comment or label |
Contributor
Author
|
Still valid I believe. |
Collaborator
|
@jtbandes sorry this never got in, if you have time to resolve the conflict I'll try to get attention to it. |
b136995 to
511c65f
Compare
Contributor
Author
|
@bjornharrtell done, thanks. |
bjornharrtell
approved these changes
Nov 27, 2025
Contributor
Author
|
@bjornharrtell thanks so much for pushing this along ❤️ Do you have an idea of when it might be available in a new release? |
Collaborator
|
@jtbandes nope I'm just a janitor. 😜 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
According to the internals docs, vtable entries are uint16 rather than int16.
This change allows reading to work when vtable entries are larger than 2^15-1 (which already works in C++). For example, the following schema is now readable:
(I ran into this bug in the wild when a user showed up with a schema having ~4500 fields, mostly
doubles.)