compiler-explorer/compiler-explorer

AI Summary: This issue requests the addition of a new configuration option for the '^S' command, specifically to enable 'compile' behavior similar to what Ctrl+Enter provides. The user believes this would be a useful and obvious feature to implement.

AI Summary: The C/C++ "Max Array" example code incorrectly uses a non-const pointer for the `y` parameter, even though the function only reads from it. The proposed solution is to change `double* y` to `const double* y` to accurately reflect its usage and improve code correctness.

AI Summary: This feature request asks for enhanced .NET compilation support in the CE environment. Specifically, it highlights the need for partial class detection, the ability to compile multiple .NET languages (like C# and VB.NET) within the same project, and improved support for various .NET framework versions. The user also suggests integrating the Roslyn compiler and enabling NuGet package management.

AI Summary: Improve the user experience of the Compiler Explorer for Rust by providing configurable hints or automatically adding code modifications to ensure assembly output is generated when expected, addressing issues caused by inlining and the lack of a main function. This involves potentially adding compiler-specific messages or automatically adding attributes like `#[inline(never)]` or `#[no_mangle]` to user code when appropriate, and handling warnings about unused main functions.

AI Summary: The task requires decoupling the image URLs used in Compiler Explorer's site templates from the template names. This involves adding a unique ID to each template, modifying the `lib/site-templates.ts` file and its type definition, updating the frontend to use the IDs, and adjusting the screenshot generation script (`etc/scripts/generate_site_template_screenshots.ts`) to correctly handle the new ID system. This change addresses the issue where special characters in template names cause incorrect image loading.

AI Summary: The Compiler Explorer project's test suite needs to be updated to explicitly await promises within the `expect(actual).resolves.toEqual(expected)` assertions. This is necessary to ensure correct test execution and prevent failures in future Vitest versions.