Skip to content

Commit 117e5fc

Browse files
committed
Add mention of where fn oom should go.
1 parent 7c2c444 commit 117e5fc

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

text/0000-kinds-of-allocators.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1162,6 +1162,12 @@ few motivating examples that *are* clearly feasible and useful.
11621162
over the underlying system allocator, while the convenience methods would truly
11631163
be convenient.)
11641164

1165+
* Should `oom` be a free-function rather than a method on `Allocator`?
1166+
(The reason I want it on `Allocator` is so that it can provide feedback
1167+
about the allocator's state at the time of the OOM. Zoxc has argued
1168+
on the RFC thread that some forms of static analysis, to prove `oom` is
1169+
never invoked, would prefer it to be a free function.)
1170+
11651171
# Unresolved questions
11661172
[unresolved]: #unresolved-questions
11671173

0 commit comments

Comments
 (0)