Forward declarations management

[andim2]

Hello,

https://github.com/gracicot/kangaru/wiki

"Note that we don't recommend forward declaring types from the kgr namespace, as we reserve the right to change a type to an alias in minor vesions. Since forward declaring an alias is not a thing in C++, this may create some incompatibility. Some details in the build system might also change between minor version, but we will not break documented usage of the kangaru cmake package or it's generation."

Is your feature request related to a problem? Please describe.
Nope (not yet).

Describe the solution you'd like
Provide an official, central, authoritative fwd.h, possibly?
I'd say it's not the job of a consumer to guesstimate library types ;-)
Though I am not sure what kind of management issues, overhead, or other problems a fwd.h approach has.
I've only just begun dabbling with this concept.

https://stackoverflow.com/questions/3935183/forward-declaration-include-on-top-of-declaration-include-classfwd-h-class-h

Describe alternatives you've considered
Manual forward declaration attempts. Not a good idea methinks.

Not a project consumer (yet) - though this might change soonish.

Thank you!

[gracicot]

Provide an official, central, authoritative fwd.h, possibly?

Thanks for submitting a report. I think this is a sound proposition, though it might also have to include the aliases.

Many newer project I wrote took this very approach, writing a fwd.h containing most forward declarations including templates types and aliases to them.

As most of my efforts are on writing kangaru v5 (which is a rewrite!), I might not have much effort/time allocated on anything major on kangaru v4 for the short and medium term. The v4 branch is planned to have one last feature release, but this might not make it depending on how much I can allocate to it. Although, I would welcome PRs for it!