search for: compile_multiple_module_with_mcjit

...lect the current use-cases and make them tests in LLVM, so that we define what is part of the stable C API and so that we won’t (inadvertently) break valid use cases". Now if you see “coupling" because of the naming of the test, they can be made in a more abstract way by naming the test “compile_multiple_module_with_mcjit.test” instead of “webkit.test”. > As a hyperbolic analogy: imagine if libjpeg required every user to add tests into its tree for their usage of the API. I believe this is already what any reasonable API would do: they would define use cases and write test. The expectation being that the clien...

> On Jul 18, 2015, at 11:27 AM, Hal Finkel <hfinkel at anl.gov> wrote: > > 2. We don't have a good set of tests for it, nor do we have a good set of tutorials/documentation for it. Our tutorials, specifically, are in C++, not in C. We could break the C API and we'd likely remain unaware for quite awhile. I think this is the most important point, that we lack testing for it.