On Monday, 5 September 2016 at 01:00:26 UTC, Walter Bright wrote:
What about using this template?
Sure, it'll work assuming the module imports all its symbols publically, but it's still not as usable as it should be. I still need to invoke it for a number of things, including member variable types.
If the member variable is templated, I need to analyse the template arguments for types to import them too.
If it is a function, I need to treat each argument as I treat a member variable.
I started a thread the other day that touches on another problem I have which this template won't solve: https://forum.dlang.org/thread/wggldyzrbwjboibin...@forum.dlang.org
At least in my use cases, it comes down to the template instance not inheriting the visibility of symbols from its template parameters. Which leads to these workarounds.
We're aiming for the goal of sub-second compile and reload times for rapid iteration, both with normal code and scripter code. Anything I have to do through templates and CTFE slows compile times down, in some cases significantly.
