OCaml good first issues

This issue proposes updating standard library interfaces, such as `Mutable`, to leverage the newly supported affine effects. The goal is to integrate this feature into existing library components for better resource management or other benefits provided by affine effects.

This issue proposes enhancing the analyzer's support for atomic operations in C. It aims to correctly handle GCC __sync builtins and C11 atomics by preventing false race warnings, performing operations on values rather than invalidating them, and treating certain statements on atomic variables as inherently atomic.

This issue proposes updating the pedantic mode in the stanc3 compiler to utilize structured diagnostics. The goal is to manage these diagnostics within a dedicated type inside Pedantic_analysis, rather than accumulating them in the Warnings.t structure. This is a cleanup task aimed at improving code organization and maintainability.

This issue proposes to improve the clarity of symbol generation in optimization passes. Currently, all passes share a single symbol generator, leading to undifferentiated `symN__` names that obscure the origin of changes. The proposed solution is to create a distinct symbol generator for each optimization pass, incorporating the pass name into the generated symbols (e.g., `sym{PASS_NAME}N__`) to make debugging and code review more manageable.

This issue proposes a significant refactoring of the base analysis code to eliminate redundant arguments. Instead of passing `ctx`, `Analyses.ask_of_ctx ctx`, `gs`, and `st` separately, the goal is to access all necessary information directly from the `ctx` argument, simplifying function signatures and reducing code duplication.

The user is inquiring about the feasibility of exporting raylib-ocaml games to WebAssembly (WASM). This suggests a need to explore the compatibility and potential modifications required for WASM compilation of OCaml code that uses the raylib bindings.

This issue proposes an enhancement to capture and display OCaml compiler errors from stderr instead of just the exit code. The goal is to parse these errors and convert them into a more user-friendly Rocq error format.

The `Camltac Eval` command in CamlTac is not correctly displaying named existential variables (evars) in its output. Instead of showing the original name of the evar, it's printing a generic placeholder like '?X2', which hinders readability and debugging.

This issue proposes adding unit tests for pure functions within the runtime library. These functions are responsible for core runtime behavior but currently lack test coverage, as indicated by a TODO comment in the code.

The current method for generating temporary filenames using `Filename.temp_file` is not robust and can lead to name clashes, especially between different plugins. The issue proposes implementing a solution for generating globally unique filenames to make name clashes highly improbable.

This issue proposes a performance optimization by detecting and replacing sequential calls to related Stan math functions with their combined, more efficient counterparts. The goal is to eliminate redundant computations when functions like `qr_Q` and `qr_R` are called consecutively, by instead using the single `qr` function. A warning mechanism is also suggested for models that continue to use the older, separate function calls.

This feature request aims to allow users to pass specific flags to the Binaryen toolchain, which is used in the Wasm compilation process. Currently, enabling features like 'multimemory' requires manual intervention in Binaryen, and this proposal suggests a more integrated way to pass such flags through the compiler.

The user is requesting the ability to define named targets in the build system, similar to how named dependencies are already supported. They also suggest a variable that could expand to the first target, drawing a parallel to Makefile functionality.

This issue proposes enhancing the `dune fmt` command to allow formatting of individual files specified on the command line. This would require a more robust implementation than the current alias, enabling formatting of files that can be changed and handling unformattable files with an option to control behavior. This change would also facilitate future features like selective formatting based on version control status.

This issue describes a problem with `dune-site` where installing a relocatable binary results in an incorrect path being reported for libraries. The user provides clear reproduction steps that demonstrate the issue when building and installing a project using `dune` and `dune-site` with the `--relocatable` flag.

The `Camltac Eval` command in OCaml is incorrectly displaying `open_constr` instead of the expected `constr` when evaluating a constructor. This suggests a potential bug in how Camltac handles or displays constructor types during evaluation.

The user is reporting an issue where local suppression of deprecation warnings (specifically warning 3) does not work when applied directly to a type re-declaration. While a global suppression works, the desired behavior is for local suppression to be effective in such cases.

This issue proposes adding support for translating early `return` statements within loops in the Aeneas verifier, provided these returns are semantically equivalent to `break` statements. The current implementation fails to translate a Rust function exhibiting this pattern, resulting in an 'Unreachable' error.

This issue proposes adding dedicated unit tests for the parser component. These tests will be integrated into the CI pipeline, and any Pull Requests that fail these tests will be blocked to ensure parser stability.

This issue proposes incorporating modulo constants (minus 1) as widening thresholds in the autotuner, inspired by a similar technique used in Astrée. The goal is to improve precision by leveraging the cyclical nature of modulo operations, particularly in scenarios like ring buffers. This change is considered a small addition with potentially significant benefits for static analysis.

The user reports that packages previously published to Opam are now missing. They have linked to a previous issue where the publication was discussed, indicating a potential issue with the Opam repository or the publishing process.

The `--experimental` flag in opengrep currently produces excessive, verbose logging when encountering syntax errors in files. This issue proposes to suppress these detailed error logs in normal mode and instead provide a concise summary of skipped files, similar to the non-experimental output.

This issue proposes removing the `string` type from the Gospel built-in types because it's not used as a model for OCaml strings, leading to potential confusion and type checking errors. The correct model for OCaml strings is `char sequence`, and the issue suggests parsing literal strings as `char sequence` as a bonus.

This issue proposes new commands to declare relationships between axioms, such as incompatibility or compatibility with Coq's logic. The goal is to improve clarity for non-logicians by providing warnings/errors for incompatible axioms and structuring the output of `Print Assumptions` to highlight certain axiom classifications.

The current parsing of constructors in OCaml modules leads to inconsistent behavior and errors, particularly when constructors like `M.true` are encountered. The issue proposes a partial fix to align the parsing of such cases with the expected behavior of unbound constructors, aiming to prevent parsing errors while maintaining backward compatibility.

The `semgrep scan --test` command does not correctly apply configured timeouts, job limits, or memory limits. These configurations are ignored when running tests in batch mode, leading to unexpected test execution times and resource consumption. The issue stems from the `commands/scan.py` file in the Semgrep Python library, which fails to propagate these settings to the underlying `semgrep-core` execution.

This issue reports a bug on Windows where the `--test` command fails due to a permission error accessing the `.semgrep\settings.xml` file. The goal is to investigate and resolve this permission issue to ensure the `--test` functionality works correctly on Windows environments.

The user is reporting that Dune exits with a non-zero status code even when the `--auto-promote` flag is used and a fixed point in the build is reached. This forces users to wrap Dune commands in `|| true` to prevent build failures in scripting contexts like opam files.

This issue describes a truncated error message in Emacs with Merlin when using OCaml 5.04 and Merlin v5.7.1-504. The provided OCaml code demonstrates a functor application that results in a type mismatch, but Merlin only displays the last line of the compiler's full error message, making debugging difficult.

This issue proposes adding parameterization support to the system. The core components like process, type, and channel definitions have been addressed, with the remaining task being to implement lifetime management for these parameters.