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.
Type annotations of arbitrary SymPy expressions
We currently support explicitly typing symbols (`TypedSymbol`) but any other expression can not be typed. Furthermore, expressions can be cast to a different type (`CastFunc`). These tools are too limited in certain circumstances. For example consider the SymPy expression `CastFunc(expr(4, 2))` and assume that `expr` is some expression which does not evaluate directly to a bare constant (this special case is addressed in !411). Because the cast removes all surrounding typing information and the argument does not contain any type hints, we can not infer the types of the constants. This in turn leads to errors during kernel generation (all constants must be typed). I suggest generalizing the `TypedSymbol` concept to allow annotating arbitrary expressions with type hints. The class should be as transparent to SymPy as possible, such that SymPy's automatic and explicit transformations are not influenced. These type annotations are not necessary in most circumstances but in some cases are apparently needed.
issue