[trivial] Windows is supported; docs said otherwise

dlang · Jul 31, 2016 · a12690a · a12690a
1 parent d7a7173
commit a12690a
Showing 1 changed file with 7 additions and 6 deletions.
diff --git a/std/experimental/allocator/mmap_allocator.d b/std/experimental/allocator/mmap_allocator.d
@@ -4,12 +4,13 @@ module std.experimental.allocator.mmap_allocator;
 // MmapAllocator
 /**
 
-Allocator (currently defined only for Posix) using $(D $(LUCKY mmap)) and $(D
-$(LUCKY munmap)) directly. There is no additional structure: each call to $(D
-allocate(s)) issues a call to $(D mmap(null, s, PROT_READ | PROT_WRITE,
-MAP_PRIVATE | MAP_ANONYMOUS, -1, 0)), and each call to $(D deallocate(b)) issues
-$(D munmap(b.ptr, b.length)). So $(D MmapAllocator) is usually intended for
-allocating large chunks to be managed by fine-granular allocators.
+Allocator (currently defined only for Posix and Windows) using $(D $(LUCKY mmap))
+and $(D $(LUCKY munmap)) directly (or their Windows equivalents). There is no
+additional structure: each call to $(D allocate(s)) issues a call to
+$(D mmap(null, s, PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_ANONYMOUS, -1, 0)),
+and each call to $(D deallocate(b)) issues $(D munmap(b.ptr, b.length)).
+So $(D MmapAllocator) is usually intended for allocating large chunks to be
+managed by fine-granular allocators.
 
 */
 struct MmapAllocator