forked from lix-project/lix
469d06f9bc
This is generally a fine practice: Putting implementations in headers makes them harder to read and slows compilation. Unfortunately it is necessary for templates, but we can ameliorate that by putting them in a separate header. Only files which need to instantiate those templates will need to include the header with the implementation; the rest can just include the declaration. This is now documenting in the contributing guide. Also, it just happens that these polymorphic serializers are the protocol agnostic ones. (Worker and serve protocol have the same logic for these container types.) This means by doing this general template cleanup, we are also getting a head start on better indicating which code is protocol-specific and which code is shared between protocols. |
||
|---|---|---|
| .. | ||
| advanced-topics | ||
| architecture | ||
| command-ref | ||
| contributing | ||
| figures | ||
| installation | ||
| language | ||
| package-management | ||
| protocols | ||
| release-notes | ||
| glossary.md | ||
| introduction.md | ||
| quick-start.md | ||
| SUMMARY.md.in | ||