Admin message

Attention: i10git will shutdown soon!

This i10git GitLab server was migrated to gitos.rrze.fau.de due to hardware issues with the current host. This affects all production repositories, including waLBerla, lbmpy, pystencils and HyTeG.

Login: Gitos supports DFN-AAI and eduGAIN. If your institution does not support either, please use our GitHub mirrors.

Onboarding: All repositories belonging to groups were migrated. To regain access, first log in to gitos.rrze.fau.de once to activate your account. Then email cs10-admin@fau.de with your old i10git and your new gitos.rrze username (the @) as shown on your respective user profiles. We will reassign your accordingly. Note: Repositories from former courses (e.g. advpt) were not migrated.

Personal repositories in individual user namespaces were not migrated. Please export these yourself before the old server is shut down.

Expected shutdown by the end of 2026. Until then, the old i10git server will still be reachable with all repositories archived (read only). However, due to the ongoing hardware issues, it may remain unreliable and will receive no further maintenance.

The parent group is archived. This project and its data are read-only.
Add source files as proper object-oriented entities
At the moment, the `SfgContext` collects all structurual components that should be written out to the generated source files, but the association of each component with the generated header file, implementation file, or both, is left implicit and only determined by the printer. This is a significant limitation, as it makes it hard to place pieces of code specifically in certain files, and requires lots of special handling when doing header-only or inline-header code generation. ## Proposal - Implement classes for modelling C++ source files as individual objects, which shall explicitly contain all structural components that should be written to that file: prelude comment, header inclusions, definitions, regular and kernel namespaces. - Change the `SfgContext` to hold one or more such source file instances. - Change the `SfgComposer` to add all code entities declared through its API to the correct file(s). - Split `SfgFunction` and `SfgMethod` into a declaration and a definition part and have `SfgComposer` add the function declaration and definition to separate source files, or to the same source file in different places, depending on the requested inlining behavior. This change automatically allows source files to contain multiple namespaces, although the `SfgComposer` shall, for the time being, stick to modelling a single primary namespace. Also, this will allow kernel namespaces to be placed in header files.
issue