Jeremy Yallop

Results 198 comments of Jeremy Yallop

I'd like to support this kind of thing, but ideally via a general mechanism of customising the generated code (#211). In the short/medium term one possibility is to generate code...

Thanks for the interesting example, @stedolan. @lpw25: > I'm curious if the same thing happens in Haskell, Oleg describes a somewhat similar example in [Impredicativity + injectivity + type case...

The [ctypes-build](https://github.com/yallop/ocaml-ctypes-build) package provides some preliminary ocamlbuild support.

Some parts of C++ are supported. Using ctypes stub generation it's possible to call overloaded functions, function templates, etc.: anything that can be called using C call syntax will work,...

It may be possible to build this atop #182, by exposing an interface to the typed representation of C code.

There's something odd about this, since whichever struct layout the compiler uses, it's always valid to read from and write to struct fields through a pointer. It seems that the...

@fdopen: I mean that packed structs aren't part of standard C, and in standard C, a program that (1) takes the address of a struct field, then (2) reads/writes through...

Thanks for the report! The issue in `sodium` arises from the use of `ocaml_bytes`; it's fixed by #622.

@aantron: #646 will eliminate these warnings.

Indeed, this is a naive implementation, and it should be possible to do considerably better. Several possible improvements, some more work than others: * Eliminate allocations from the loop (which...