This looks awesome! Just got a question about versioning of the future_syntax preprocessor. I like how easy it is to specify it in the dune files, but I’m concerned about what will happen if one day you want to deprecate this preprocessor and support yet another “future_syntax”.
For example, in the python2 community, it’s common to see people specifically select which future syntaxes to use by writing:
from __future__ import print_function