David Sheets
David Sheets
It would be nice to have `ocaml_bytes_opt : Bytes.t option Ctypes_static.ocaml typ` and `ocaml_string_opt : string option Ctypes_static.ocaml typ` so that null pointers can be passed in place of OCaml-managed...
Support for Big Endian, Little Endian, and Host Endian layouts would bring ctypes into feature parity on primitive types with cstruct. Is there currently endianness support somehow?
When writing functions that coerce from one type to another, especially in cross-platform bindings, it is common to have a type mismatch in coercions. Currently, this error manifests as a...
In [binding OS X CoreFoundation](https://github.com/dsheets/ocaml-osx-cf), in particular the writing of the views for the pointer-parametric [CFArray functor](https://github.com/dsheets/ocaml-osx-cf/blob/master/lib/cf.ml#L117-L136), I have realized (in consultation with @yallop) that there is no facility for...
Right now, `Foreign.funptr` has an optional argument `?runtime_lock`. This parameter has no 'obvious' default value because its use is very context-dependent and its correct use is critical with non-obvious behavior...
Right now, there is no way to quietly use `ocaml_bytes` or `ocaml_string` in an API that expects `UInt8 *` or similar -- only `char *` is workable -- even if...
What functions can consume `Cstubs.Types.TYPE.const` and return something useful? Only `Cstubs.Types.TYPE.enum` as far as I can tell. What if you have constants that were not in an `enum`? For instance,...
It's frightening but it does exist. :-( See https://tools.ietf.org/html/rfc3492 and https://tools.ietf.org/html/rfc5891. This might want to be a codec lib that we depend on in some future utopia.
There should be interface functions to operate over path segments and provide the same kind of services that are available to query components.