summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoramesgen <amesgen@amesgen.de>2023-01-16 20:28:20 +0100
committerMarge Bot <ben+marge-bot@smart-cactus.org>2023-02-14 11:27:14 -0500
commitc399ccd97892fd536abf64b03f467e8fe4cc50e5 (patch)
tree4096fa21be1e35cb222f2f501f2042f319f5a518
parent16adc349b7f1d7185a74eedc2e3e3d0cffa5db84 (diff)
downloadhaskell-c399ccd97892fd536abf64b03f467e8fe4cc50e5.tar.gz
Mention new `Foreign.Marshal.Pool` implementation in User's Guide
-rw-r--r--docs/users_guide/exts/ffi.rst8
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/users_guide/exts/ffi.rst b/docs/users_guide/exts/ffi.rst
index 37d96a0a68..4c4b6f7a49 100644
--- a/docs/users_guide/exts/ffi.rst
+++ b/docs/users_guide/exts/ffi.rst
@@ -807,11 +807,9 @@ the different kinds of allocation perform with GHC.
the other forms of allocation above.
``Foreign.Marshal.Pool``
- Pools are currently implemented using ``malloc/free``, so while they
- might be a more convenient way to structure your memory allocation
- than using one of the other forms of allocation, they won't be any
- more efficient. We do plan to provide an improved-performance
- implementation of Pools in the future, however.
+ Pools can be a more convenient way to structure your memory
+ allocation than using one of the other forms of allocation. They are
+ backed by the RTS internal arena instead of ``malloc/free``.
.. _ffi-threads: