Displaying 2 results from an estimated 2 matches for "llfunction_variants".
2008 Mar 16
0
[LLVMdev] improving the ocaml binding's type safety
..."type 'a whatever". The
phantom type would be enough to distinguish everything. For instance,
lablgtk has a "type 'a obj" that they use as the base type for all of
their variants, which I might copy. We can even hide this type by
naming the variants something like "llfunction_variants" and then
"type llfunction = llfunction_variants obj" to have roughly the same
interface as before.
What about putting the types (and functions) in modules, like
ModuleProvider? It'd be like my scheme to break up llvm.ml into
multiple files without actually splitting it up :) Th...
2008 Mar 16
2
[LLVMdev] improving the ocaml binding's type safety
Erick,
After some experimentation, I'd prefer the closed system. LLVM has
some type peculiarities like the commonality between CallInst and
InvokeInst. I find that the closed type system lets me express such
constraints more naturally. Expressing these constraints explicitly in
the open system involves annotating the C++ class hierarchy with extra
variants which are unnecessary in