docs(allocator/address): improve docs for Address::from_ptr#15311
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
There was a problem hiding this comment.
Pull Request Overview
This PR enhances the documentation for the Address::from_ptr method by clarifying its usage and potential pitfalls. The update emphasizes that this method should be used as an escape hatch, with preference given to GetAddress::address for more stable address retrieval.
Key Changes:
- Reorganized and expanded documentation to highlight best practices
- Added comprehensive example demonstrating the difference between
Address::from_ptrandGetAddress::address - Clarified behavior when AST nodes are stored in
VecvsBox
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
CodSpeed Performance ReportMerging #15311 will not alter performanceComparing Summary
Footnotes |
Merge activity
|
Improve the docs for `Address::from_ptr` to highlight why it's best avoided. This was prompted by me noticing that Rolldown uses `Address::from_ptr` (rolldown/rolldown#6245).
f2b6b90 to
ed0e023
Compare

Improve the docs for
Address::from_ptrto highlight why it's best avoided.This was prompted by me noticing that Rolldown uses
Address::from_ptr(rolldown/rolldown#6245).