package devkit
Development kit - general purpose library
Install
Dune Dependency
Authors
Maintainers
Sources
devkit-1.20240429.tbz
sha256=222f8ac131b1d970dab7eeb2714bfd6b9338b88b1082e6e01c136ae19e7eaef4
sha512=c9e6d93e3d21e5530c0f4d5baca51bf1f0a5d19248f8af7678d0665bb5cdf295d7aaaaa3e50eb2e44b8720e55097cc675af4dc8ec45acf9da39feb3eae1405d5
doc/src/devkit.ocamlnet_lite/netsys_types.ml.html
Source file netsys_types.ml
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
(* WARNING! THIS IS A COPY OF NETSYS_TYPES.MLI! *) (** Types for all Netsys modules *) (** {2 Bytes and characters} *) (** Remember that up to OCaml-4.01 there was only the [string] type, and strings were mutable (although frequently used as if there were immutable). Since OCaml-4.02 there is the immutable [string] and the mutable [bytes] type. The general strategy for switching to the string/bytes scheme is to replace [string] everywhere with [bytes], and to provide additional functions taking strings as input or output where it makes sense. There are exceptions, though, e.g. when the string acts as a key in a data structure. The type name "string" also occurs in function names (e.g. "get_string") and in variant names (e.g. [String_case]). As we want to be backward compatible, we keep the old names for functions on [bytes], and mark them as deprecated. *) type tbuffer = [ `Bytes of Bytes.t | `String of Bytes.t ] (** A tagged buffer. Note that the [`String] case is deprecated, and only provided for backward compatibility. *) type tstring = [ `Bytes of Bytes.t | `String of string ] (** A tagged string which is considered as immutable. See also the support module {!Netstring_tstring}. *)
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>