-
Notifications
You must be signed in to change notification settings - Fork 374
Closed
Labels
Description
Feature Request
Align Buffer read/write API with Java naming style
Is your feature request related to a problem? Please describe
Current JavaScript buffer read/write methods do not use read* / write* prefixes. This makes the API less explicit and less consistent with Java and other xlang implementations.
Describe the solution you'd like
Refactor JavaScript buffer APIs to use explicit read* / write* method names.
Requirements:
- Rename write-side methods (for example
int8,int16,uint32) towriteInt8,writeInt16,writeUint32, etc. - Rename read-side methods using the same rule (
read*). - Perform a one-shot breaking rename: do not keep old method names, aliases, or deprecation shims.
- Update all internal call sites, tests, docs, and examples in the same change.
- Keep runtime behavior and performance unchanged.
Describe alternatives you've considered
- Keep old names as aliases during a transition period.
This was rejected. We want a clean one-time migration without compatibility aliases.
Additional context
This issue is specifically for API naming consistency and migration cleanup.
Reactions are currently unavailable