package core
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=6f7bbdda1d97f2f542a45331f062127dd5264d6ed73ece7b2c6b330785dfc991
doc/core/Core/Bigstring/index.html
Module Core.Bigstring
String type based on Bigarray, for use in I/O and C-bindings.
Types and exceptions
Type of bigstrings
include Ppx_compare_lib.Comparable.S with type t := t
include Ppx_quickcheck_runtime.Quickcheckable.S with type t := t
val quickcheck_generator : t Base_quickcheck.Generator.tval quickcheck_observer : t Base_quickcheck.Observer.tval quickcheck_shrinker : t Base_quickcheck.Shrinker.ttype t_frozen = tType of bigstrings which support hashing. Note that mutation invalidates previous hashes.
include module type of Base_bigstring
with type t := t
and type t_frozen := t_frozen
Types and exceptions
include Ppx_compare_lib.Comparable.S with type t := t
include Sexplib0.Sexpable.S with type t := t
val t_of_sexp : Sexplib0.Sexp.t -> tval sexp_of_t : t -> Sexplib0.Sexp.tval hash_fold_t_frozen :
Ppx_hash_lib.Std.Hash.state ->
t_frozen ->
Ppx_hash_lib.Std.Hash.stateval hash_t_frozen : t_frozen -> Ppx_hash_lib.Std.Hash.hash_valueval sexp_of_t_frozen : t_frozen -> Sexplib0.Sexp.tval t_frozen_of_sexp : Sexplib0.Sexp.t -> t_frozeninclude Base.Equal.S with type t := t
val equal : t Base.Equal.equalCreation and string conversion
init n ~f creates a bigstring t of length n, with t.{i} = f i.
val of_string : ?pos:Base.int -> ?len:Base.int -> Base.string -> tof_string ?pos ?len str
val of_bytes : ?pos:Base.int -> ?len:Base.int -> Base.bytes -> tof_bytes ?pos ?len str
val to_string : ?pos:Base.int -> ?len:Base.int -> t -> Base.stringto_string ?pos ?len bstr
val to_bytes : ?pos:Base.int -> ?len:Base.int -> t -> Base.bytesto_bytes ?pos ?len bstr
concat ?sep list returns the concatenation of list with sep in between each.
Checking
val check_args :
loc:Base.string ->
pos:Base.int ->
len:Base.int ->
t ->
Base.unitcheck_args ~loc ~pos ~len bstr checks the position and length arguments pos and len for bigstrings bstr.
val get_opt_len : t -> pos:Base.int -> Base.int Base.option -> Base.intget_opt_len bstr ~pos opt_len
Accessors
Blitting
blit ~src ?src_pos ?src_len ~dst ?dst_pos () blits src_len characters from src starting at position src_pos to dst at position dst_pos.
include Base.Blit.S with type t := t
module To_string : sig ... endmodule From_string :
Base.Blit.S_distinct with type src := Base.string with type dst := tmodule To_bytes :
Base.Blit.S_distinct with type src := t with type dst := Base.bytesmodule From_bytes :
Base.Blit.S_distinct with type src := Base.bytes with type dst := tmemset t ~pos ~len c fills t with c within the range [pos, pos + len).
Memcmp
memcmp t1 ~pos1 t2 ~pos2 ~len is like compare t1 t2 except performs the comparison on the subregions of t1 and t2 defined by pos1, pos2, and len.
memcmp_bytes, for efficient memcmp between Bigstring and Bytes data.
Search
find ?pos ?len char t returns Some i for the smallest i >= pos such that t.{i} = char, or None if there is no such i.
Same as find, but does no bounds checking, and returns a negative value instead of None if char is not found.
Accessors for parsing binary values, analogous to Binary_packing
These are in Bigstring rather than a separate module because:
1. Existing Binary_packing requires copies and does not work with bigstrings. 2. The accessors rely on the implementation of bigstring, and hence should change should the implementation of bigstring move away from Bigarray. 3. Bigstring already has some external C functions, so it didn't require many changes to the jbuild ^_^.
In a departure from Binary_packing, the naming conventions are chosen to be close to C99 stdint types, as it's a more standard description and it is somewhat useful in making compact macros for the implementations. The accessor names contain endian-ness to allow for branch-free implementations
<accessor> ::= <unsafe><operation><type><endian> <unsafe> ::= unsafe_ | '' <operation> ::= get_ | set_ <type> ::= int8 | uint8 | int16 | uint16 | int32 | uint32 | int64 | uint64 <endian> ::= _le | _be | ''
The unsafe_ prefix indicates that these functions do no bounds checking and silently truncate out-of-range numeric arguments.
16-bit methods
32-bit methods
Similar to the usage in binary_packing, the below methods are treating the value being read (or written), as an ocaml immediate integer, as such it is actually 63 bits. If the user is confident that the range of values used in practice will not require 64-bit precision (i.e. Less than Max_Long), then we can avoid allocation and use an immediate. If the user is wrong, an exception will be thrown (for get).
64-bit signed values
64-bit unsigned values
32-bit methods with full precision
val get_int32_t_le : t -> pos:Base.int -> Base.Int32.tval get_int32_t_be : t -> pos:Base.int -> Base.Int32.tval set_int32_t_le : t -> pos:Base.int -> Base.Int32.t -> Base.unitval set_int32_t_be : t -> pos:Base.int -> Base.Int32.t -> Base.unitval unsafe_get_int32_t_le : t -> pos:Base.int -> Base.Int32.tval unsafe_get_int32_t_be : t -> pos:Base.int -> Base.Int32.tval unsafe_set_int32_t_le : t -> pos:Base.int -> Base.Int32.t -> Base.unitval unsafe_set_int32_t_be : t -> pos:Base.int -> Base.Int32.t -> Base.unit64-bit methods with full precision
val get_int64_t_le : t -> pos:Base.int -> Base.Int64.tval get_int64_t_be : t -> pos:Base.int -> Base.Int64.tval set_int64_t_le : t -> pos:Base.int -> Base.Int64.t -> Base.unitval set_int64_t_be : t -> pos:Base.int -> Base.Int64.t -> Base.unitval unsafe_get_int64_t_le : t -> pos:Base.int -> Base.Int64.tval unsafe_get_int64_t_be : t -> pos:Base.int -> Base.Int64.tval unsafe_set_int64_t_le : t -> pos:Base.int -> Base.Int64.t -> Base.unitval unsafe_set_int64_t_be : t -> pos:Base.int -> Base.Int64.t -> Base.unitmodule Int_repr : sig ... endmodule Private : sig ... endCreation and string conversion
val create : ?max_mem_waiting_gc:Core__.Byte_units0.t -> Base.Int.t -> tcreate length
sub_shared ?pos ?len bstr
Reading/writing bin-prot
These functions write the "size-prefixed" bin-prot format that is used by, e.g., async's Writer.write_bin_prot, Reader.read_bin_prot and Unpack_buffer.Unpack_one.create_bin_prot.
val write_bin_prot :
t ->
?pos:Base.Int.t ->
'a Bin_prot.Type_class.writer ->
'a ->
Base.Int.twrite_bin_prot t writer a writes a to t starting at pos, and returns the index in t immediately after the last byte written. It raises if pos < 0 or if a doesn't fit in t.
val read_bin_prot :
t ->
?pos:Base.Int.t ->
?len:Base.Int.t ->
'a Bin_prot.Type_class.reader ->
('a * Base.Int.t) Or_error.tThe read_bin_prot* functions read from the region of t starting at pos of length len. They return the index in t immediately after the last byte read. They raise if pos and len don't describe a region of t.
val read_bin_prot_verbose_errors :
t ->
?pos:Base.Int.t ->
?len:Base.Int.t ->
'a Bin_prot.Type_class.reader ->
[ `Invalid_data of Error.t | `Not_enough_data | `Ok of 'a * Base.Int.t ]Destruction
val unsafe_destroy : t -> Base.Unit.tunsafe_destroy bstr destroys the bigstring by deallocating its associated data or, if memory-mapped, unmapping the corresponding file, and setting all dimensions to zero. This effectively frees the associated memory or address-space resources instantaneously. This feature helps working around a bug in the current OCaml runtime, which does not correctly estimate how aggressively to reclaim such resources.
This operation is safe unless you have passed the bigstring to another thread that is performing operations on it at the same time. Access to the bigstring after this operation will yield array bounds exceptions.
val unsafe_destroy_and_resize : t -> len:Base.Int.t -> tunsafe_destroy_and_resize bstr ~len reallocates the memory backing bstr and returns a new bigstring that starts at position 0 and has length len. If len is greater than length bstr then the newly allocated memory will not be initialized.
Similar to unsafe_destroy, this operation is safe unless you have passed the bigstring to another thread that is performing operations on it at the same time. Access to bstr after this operation will yield array bounds exceptions.
val get_tail_padded_fixed_string :
padding:Base.Char.t ->
t ->
pos:Base.Int.t ->
len:Base.Int.t ->
Base.Unit.t ->
Base.String.tSimilar to Binary_packing.unpack_tail_padded_fixed_string and .pack_tail_padded_fixed_string.
val set_tail_padded_fixed_string :
padding:Base.Char.t ->
t ->
pos:Base.Int.t ->
len:Base.Int.t ->
Base.String.t ->
Base.Unit.tval get_head_padded_fixed_string :
padding:Base.Char.t ->
t ->
pos:Base.Int.t ->
len:Base.Int.t ->
Base.Unit.t ->
Base.String.tval set_head_padded_fixed_string :
padding:Base.Char.t ->
t ->
pos:Base.Int.t ->
len:Base.Int.t ->
Base.String.t ->
Base.Unit.tmodule Unstable : sig ... endmodule Stable : sig ... end