Zig good first issues

This issue is titled 'Where u at' and contains only ASCII art. It has labels indicating it's a documentation issue, a good first issue, and a question. The ASCII art itself doesn't provide any technical context, suggesting the issue might be a placeholder or a humorous way to ask for something.

This issue proposes enhancing the display of documentation shown on hover by implementing rich markdown rendering and highlighting. Currently, the text appears raw, and the suggestion is to leverage a project like 'termimad' to achieve a more visually appealing and readable presentation.

This issue requests that the `openreliant install` tool be updated to recognize additional regional releases of the game StarLancer, specifically German and Japanese versions. This involves identifying the correct disc sizes for these releases and potentially addressing a decompression error associated with the German version.

This issue proposes adding support for exemplars in the OpenTelemetry SDK's metrics collection. Currently, there is no functionality for exemplars, indicated by existing TODO comments in the codebase. Implementing this would align the SDK with OpenTelemetry specifications for richer metric data.

This issue addresses several minor gaps and inconsistencies found in shell completion scripts (Bash and Zsh) after previous merges. It also includes a fix for a test that was too permissive and updates to the README to correctly instruct users on macOS regarding shell configuration and Zsh completion setup.

This issue proposes several improvements to the FreeRTOS integration for RP2040 and RP2350 targets. Key areas include expanding Zig wrapping functions, migrating configuration options to Zig build files, offering more allocator selections, implementing multicore support, and addressing missing symbols for the RP2350 RISC-V port.

This issue proposes adding support for CBOR (Concise Binary Object Representation) serialization and deserialization to the project. CBOR is an IETF standard designed for efficient data representation, and the contributor intends to use it for smaller data sizes.

This issue proposes adding essential regular expression functions (REGEXP_EXTRACT, REGEXP_REPLACE, REGEXP_MATCHES) to csvql, which are currently missing. These functions are crucial for text cleaning and data manipulation, enabling users to extract, replace, and match patterns within data, a common task that currently requires external processing. The implementation presents a significant challenge due to Zig's lack of a standard regex library, requiring a choice between building a custom engine, vendoring a C library, or omitting the feature.

This issue requests the creation of a new icon for the OpenReliant project. The icon needs to be versatile, working across various sizes and platforms, and should visually represent space combat and carriers in a style reminiscent of StarLancer without using any of the game's original assets. The contributor should provide source files and various PNG exports, with optional platform-specific formats.

The user is requesting session persistence for `zmx`, similar to how `zellij` handles it. They experienced a loss of all session data, including metadata, after a machine reboot due to an OOM error. The suggestion is to explore persisting at least some session data, like metadata, to prevent complete loss after crashes.

A user is requesting the addition of the GameSir G7 Pro controller to the list of supported devices for the padctl project. This implies a need for driver or configuration support for this specific controller.

The user is requesting the addition of the Razer Wolverine V3 Pro controller to the padctl supported devices. This is a feature request for expanding hardware compatibility.

This issue tracks the ongoing effort to expand the supported programming languages within a project. The "Shipped" section lists languages already implemented, while the "Plan" section outlines languages yet to be added. The maintainers are also soliciting community input on which languages users would prefer to see supported next.

This issue proposes a new feature to address UI instability in a file list popup. The goal is to prevent the list and its borders from jumping around during file selection by introducing a fixed-size box for the list. Users will be able to configure this behavior via a `config.toml` file, choosing between auto or fixed sizing.

This issue requests the creation of new example mods for OpenReliant's modding features that currently lack them. The goal is to provide clear demonstrations for mod makers on how to implement custom droids with unique faces and voices, texture replacements, interface modifications, and music changes. Each example is considered a small, independent task suitable for individual pull requests.

This issue aims to track and implement missing built-in functions for the Zig compiler, using modern Roc API conventions. The goal is to ensure all necessary built-ins are declared, implemented, supported by backends and interpreters, and tested, while prioritizing pure and Try-returning functions over effectful collection variants.

This issue proposes adding a compiler warning and `roc fmt` behavior to handle redundant explicit exposures of a type module's main type. When a type module is imported, its main type is automatically brought into scope, making explicit re-exposure unnecessary and potentially confusing.

This issue requests that when `csvql` is run with only a CSV file path (no SQL query), it should provide a more informative summary before the data preview. This summary should include row and column counts, column names with inferred types and potentially null/distinct counts, and 2-3 example queries tailored to the CSV's structure. The goal is to make the no-query mode a useful data exploration tool.

The csvql tool currently only supports the MEDIAN aggregate function, which is the 50th percentile. Users need additional functions like QUANTILE, PERCENTILE_CONT, and MODE to analyze data distributions more effectively, especially for identifying outliers and common values in categorical data. The underlying machinery for buffering and selecting values already exists, making this a feasible enhancement.

This issue requests the addition of functions like NOW(), CURRENT_DATE, and CURRENT_TIMESTAMP to allow queries to reference the current date and time. Currently, users must manually calculate and insert literal dates, leading to stale queries and difficulties for dynamic use cases like agent interactions. The proposed solution involves implementing these functions as zero-argument scalars, evaluated once per query for consistency.

This issue proposes adding six new string functions to csvql: LTRIM, RTRIM, LEFT, RIGHT, REPEAT, and POSITION/INSTR. These functions are considered 'neighbors' to existing functions and are needed for common CSV cleanup tasks like extracting suffixes or finding delimiter positions, which are currently not directly supported.

This issue requests the addition of a `NULLIF` function to `csvql` to handle sentinel values in CSV data. Currently, `csvql` lacks a way to convert specific placeholder values (like -1 or 0) into NULLs, leading to incorrect aggregations. The proposed solution is to implement `NULLIF` which returns a field or an empty string (csvql's NULL) based on a comparison with a literal value.

This issue requests the addition of two new scalar functions, SQRT (square root) and POWER (exponentiation), to the SQL engine. The implementation should follow the pattern of existing scalar functions like ABS, CEIL, and FLOOR, involving updates to `src/scalar.zig`, the SQL Reference in `README.md`, and a new unit test.

This issue proposes a syntax change for destructuring list segments in the Roc programming language. The current `[first, .. as rest]` syntax should be updated to `[first, ..rest]` to align with the new spread syntax being introduced in a related issue.

This issue requests adding documentation comments to public items within the `src/widget` directory. The goal is to improve code clarity by explaining the behavior of each widget, not just its name. Developers are asked to claim individual files and submit separate pull requests for each.

This issue requests the addition of missing unit tests for the `textinput.zig` widget. Specifically, tests are needed to cover cursor movement, character deletion, password echo modes, and horizontal scrolling behavior. The goal is to improve test coverage and ensure the robustness of these functionalities.

This issue describes a bug in the Zig text input widget where Ctrl+A, Ctrl+E, Ctrl+K, and Ctrl+U are incorrectly treated as printable characters and inserted into the text field instead of executing their intended shortcut actions. The problem stems from the `isPrintable()` function not properly handling modifier keys, causing these shortcuts to be processed as regular character input before reaching the keymap.

The TextInput widget in Zig version 0.16.0 on Linux incorrectly handles Alt+Left/Right and Alt+Backspace key combinations. Instead of performing word-based navigation or deletion as expected, these combinations are being intercepted by character-based bindings, causing them to move or delete a single character. This is due to the `key.matches()` function allowing extra modifiers and the order of binding checks in `TextInput.update()`.

The tests for the `list.zig` file are not being included in the `build.zig` file, which prevents `zig build test` and `zig build test-widget` from running them. This means that any regressions in the List widget might go unnoticed by CI. The suggested fix is to add the `list.zig` tests to the appropriate test suite in `build.zig`.

This issue proposes adding support for anonymous index parameters using Zig tuples. This would allow for more flexible and concise ways to pass parameters to indexes, potentially improving code readability and reducing boilerplate.