:88    portable experimentalNone+Mode of mapping. Four cases are supported. (file is mapped read-write, if file does + not exist it will be created with default ) permissions, region parameter specifies ( size, if file size is lower it will be  extended with zeros 'file is mapped read-write, but changes  aren'&t propagated to disk, file must exist %file is mapped read-write, file must  exist $file is mapped read-only, file must  exist Memory mapping granularity. GSet file size in system specific manner. It is guaranteed to be called 1 only with new size being at least current size. (Get file size in system specific manner =Unmap region of memory. Size must be the same as returned by A mmap. If size is zero, does nothing (treats pointer as invalid) DMmemory maps file from handle, using mode, starting offset and size 8Should open file given as CString in mode given as CInt The - function maps a file or device into memory,  returning a tuple (ptr,rawsize,offset,size) where:  ptr is pointer to mmapped region  rawsize7 is length (in bytes) of mapped data, rawsize might be ( greater than size because of alignment  offset tell where your data lives: plusPtr ptr offset  size your data length (in bytes) If  fails for some reason, a  is used. Use munmapFilePtr ptr rawsize to unmap memory. <Memory mapped files will behave as if they were read lazily ; pages from the file will be loaded into memory on demand. 9Memory map region of file using autounmap semantics. See  % for description of parameters. The action will be  executed with tuple  (ptr,size)! as single argument. This is the ? pointer to mapped data already adjusted and size of requested ) region. Return value is that of action. &Maps region of file and returns it as . See  for details. &Maps region of file and returns it as  . File is  mapped in in  mode. See  for details. The  % function maps a file or device into @ memory, returning a list of tuples with the same meaning as in  function . BChunks are really mapped into memory at the first inspection of a C chunk. They are kept in memory while they are referenced, garbage $ collector takes care of the later. &Maps region of file and returns it as  . File is  mapped in in  mode. See   for  details. AUnmaps memory region. As parameters use values marked as ptr and  rawsize in description of .  'handle from c_system_io_mmap_file_open mode $starting offset, must be nonegative "length, must be greater than zero Astarting pointer to byte data, nullPtr on error (plus errno set)  | Used in finalizers file path, system encoding mode as 0, 1, 2, fromEnum 7file handle returned, nullPtr on error (and errno set) ' | Used in finalizers, to close handle name of file to mmap  access mode )range to map, maps whole file if Nothing (ptr,rawsize,offset,size) name of file to mmap  access mode )range to map, maps whole file if Nothing action to run result of action name of file to map  access mode )range to map, maps whole file if Nothing ,foreign pointer to beginning of raw region, + offset to your data and size of your data name of file to map )range to map, maps whole file if Nothing bytestring with file contents name of file to mmap  access mode )range to map, maps whole file if Nothing (ptr,offset,size)  name of file to map )range to map, maps whole file if Nothing bytestring with file content pointer rawsize             !"#$%& mmap-0.5.9System.IO.MMapMode ReadWriteEx WriteCopy ReadWriteReadOnly mmapFilePtrmmapWithFilePtrmmapFileForeignPtrmmapFileByteStringmmapFileForeignPtrLazymmapFileByteStringLazy munmapFilePtrc_system_io_granularityc_system_io_extend_file_sizec_system_io_file_sizec_system_io_mmap_munmapc_system_io_mmap_mmapc_system_io_mmap_file_openbaseForeign.C.Error throwErrnoGHC.ForeignPtr ForeignPtrbytestring-0.10.0.2Data.ByteString.Internal ByteStringData.ByteString.Lazy.Internalc_system_io_mmap_munmap_funptrc_system_io_mmap_file_closesanitizeFileRegioncheckModeRegionmmapFileForeignPtrLazyChunkchunks chunkSize mmapFileOpen castIntToPtr