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.
Improve Support for Arrays and Array-Like Expressions
## Improve Type Inference for Array Literals **DONE** The `Typifier` currently has only limited support for inferring the type of array initializer lists (`PsArrayInitList`) when no type information about their entries is given. This is especially the case for declarations of arrays of numeric constants, e.g. ``` ps.Assignment(sp.Symbol("arr"), (1, 2, 3, 4)) ``` *should* translate to C code as ``` double arr[] = { 1., 2., 3., 4. }; ``` provided that `float64` is the `default_dtype`. Currently, the type of `arr` cannot be inferred. When array literals such as this occur inline within an expression, such as `x + {1, 2, 3, 4}[idx]`, type inference is also unreliable. **Requirement:** If the type of an array literal's entries, and therefore the array itself, cannot be inferred from its entries, it should be inferred from the enclosing context in the same way as for scalar constants. ~ ## Parsing of SymPy Matrices and Tensor-Like objects Currently, pystencils only parses `sp.Tuple` as an array literal. The implementation of `FreezeExpressions` should be extended such that immutable SymPy [matrices](https://docs.sympy.org/latest/modules/matrices/immutablematrices.html) and [tensor-like objects](https://docs.sympy.org/latest/modules/tensor/array.html#sympy.tensor.array.ImmutableDenseNDimArray) (which qualify as expressions) are also parsed as array literals. ## Documentation of Array-Parsing Capabilities The new capabilities of pystencils to handle array-like objects have to be documented. Add a section about arrays to the [symbolic language documentation](https://da15siwa.pages.i10git.cs.fau.de/dev-docs/pystencils-nbackend/api/symbolic_language/index.html).
issue