Steps to introduce optimized swig-free jitting

[Martin Sandve Alnæs]

After some investigations and thinking, these are steps I think can be done as separate refactoring steps in this order, each step resulting a still functional code. I've created issues for some of the pieces that can be done independently.

A) Use factory functions to construct ufc objects from python which will work with ctypes later: https://bitbucket.org/fenics-project/ffc/issues/89/generate-factory-functions-to-construct

B) Using ctypes to load jit compiled classes: https://bitbucket.org/fenics-project/ffc/issues/91/use-ctypes-to-load-jit-compiled-classes

C) Generate elements and forms separately: https://bitbucket.org/fenics-project/ffc/issues/90/split-generation-of-elements-and-forms

[Martin Sandve Alnæs]

Milestone 1.7 may be optimistic. Doing A+B will provide most of the benefits, and the benefits of doing C can be profiled and reconsidered then.

[Martin Sandve Alnæs]

Johannes has said he can take a look at this.

[Prof Garth Wells]

Removing milestone: 1.7 (automated comment)

[Prof Garth Wells]

Is this now resolved?

[Johannes Ring]

Sorry, issue #90 not resolved.

[Martin Sandve Alnæs]

We can mark this as resolved even though (C) is not done, since it has its own issue and swig-free jitting has been accomplished.