Added v24.0.3.1 to wgpu-native

[nahahahah]

Added add_versions("v24.0.3+1", ...) for each already supported platforms for the wgpu-native package

[gemini-code-assist]

Summary of Changes

Hello @hardcore-thinking, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily aims to update the wgpu-native package definition by introducing support for version v24.0.3+1 across all currently supported platforms. Additionally, it also incorporates version v27.0.2+0, ensuring broader compatibility and access to the latest features or fixes for these specific wgpu-native releases.

Highlights

• New wgpu-native Version Added: The wgpu-native package now supports version v24.0.3+1.
• Additional wgpu-native Version Added: Support for wgpu-native version v27.0.2+0 has also been introduced.
• Cross-Platform Compatibility: Both new versions (v24.0.3+1 and v27.0.2+0) have been added for all existing supported platforms, including various Windows, MinGW, Linux, and macOS architectures.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds versions v24.0.3+1 and v27.0.2+0 to the wgpu-native package for all supported platforms. The changes are correct and maintain the descending order of versions. However, the PR title and description are slightly misleading as they only mention the addition of v24.0.3+1 (with a typo in the title as v24.0.3.1), while v27.0.2+0 is also added. It would be good to update them to reflect the full scope of changes. Additionally, I've added a comment regarding the maintainability of the xmake.lua file. The current structure requires duplicating version additions across multiple platform blocks, which is error-prone. A refactoring to a more data-driven approach would make future updates much easier.

[gemini-code-assist]

This file has a lot of repeated add_versions blocks for different platforms. Adding a new version, as done in this PR, requires manually adding lines in 8 different places. This is tedious and error-prone.

To improve maintainability, consider refactoring this to be more data-driven. You could define all versions and their platform-specific hashes in a central table at the top of the file, and then iterate through this table in each platform block.

For example:

-- Define all versions and hashes in one place, in descending order
local versions_with_hashes = {
    { version = "v27.0.2+0", hashes = {
        ["windows-x64"] = "0df0231284cd9ab59dfc382f435caf1275f4372ae0635ef1261d6fe1d58c5a0e",
        ["windows-x86"] = "542fe3a3e88e617acad2f34d129f0203132b6b175af015cba977dfbee75ccbff",
        -- ... other platforms
    }},
    { version = "v25.0.2+1", hashes = { ... } },
    -- ... other versions
}

-- Helper function to add versions for a specific platform
function add_pkg_versions(plat, arch)
    local key = plat .. "-" .. arch -- Or another mapping that fits your needs
    for _, v_info in ipairs(versions_with_hashes) do
        if v_info.hashes[key] then
            add_versions(v_info.version, v_info.hashes[key])
        end
    end
end

-- Then, in each platform block, call the helper
if is_plat("windows") and is_arch("x64") then
    add_urls("...")
    add_pkg_versions("windows", "x64")
end

This would centralize version management, making future updates much simpler and safer.