diff options
| author | bors-servo <release+servo@mozilla.com> | 2014-02-05 22:19:43 -0500 |
|---|---|---|
| committer | bors-servo <release+servo@mozilla.com> | 2014-02-05 22:19:43 -0500 |
| commit | 17bc467b834f72612a9b8ae4d76f5b67a567fd46 (patch) | |
| tree | 25979ee52113f54c2f2da952573b8b6d1ff8cd57 /src/components/script/dom/processinginstruction.rs | |
| parent | 1dbc73ea1c5ab395d03934024e3f1a773b357032 (diff) | |
| parent | 78d2118f4728cd194b90b8b5d499bd6486ac71a9 (diff) | |
| download | servo-17bc467b834f72612a9b8ae4d76f5b67a567fd46.tar.gz servo-17bc467b834f72612a9b8ae4d76f5b67a567fd46.zip | |
auto merge of #1626 : kmcallister/servo/flowlist, r=pcwalton
r? @pcwalton
Some points of concern:
* Is this really memory-safe? Is there a way to access a stale `Rawlink` that doesn't exist in the normal `DList` code?
* Is it okay to coerce both `~Flow` and `&Flow` to `(uint, uint)` (or the moral equivalent) and compare them? Will a given `Flow` always have the same (obj, vtable) regardless of whether it's obtained through `~Flow` or `&Flow`?
Diffstat (limited to 'src/components/script/dom/processinginstruction.rs')
0 files changed, 0 insertions, 0 deletions