Closed dangmoody closed 4 years ago
I'm not going to be doing this for now.
I think it's going to be better releasing actual code for people to use, instead of an EXE which people have to run. I think people will be more OK with that. This also means that the generator only needs to run on the machines of those who are working on the math library itself.
All the functions that the generator generates are inline
d anyway meaning that any function not called won't be included in the compile. This should mean that we can ship the math library as is with all the code included and compile times won't take the hit.
I have a branch called config
that contains a copy of the generator will the option to specify what types to make etc. I'll be looking to keep this updated so that I can evaluate over time. While there are clearly benefits to being able to specify exactly what code you want to generate I don't think it's worth it to have as part of the main release yet.
Would it be more beneficial to have users run the generator locally so that they can only have the math types they need in their codebase?
The main advantage of this would be that the user only has the code they care about in their codebase, meaning less code bloat.
This would have to be done via some kind of config file, which specifies which types and features the user wants the generator to generate.