proof of concept: Encode and Decode using the libwebp library via WASM

[bep]

Note that this works, but the building blocks are quickly thrown together just to get a sense if this makes sense to go forward with.

See #12843

[gemini-code-assist]

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

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.

[bep]

As to performance:

• I have pushed an update that uses Wazero's latest con current compiler, which gets the "init WASM" step down from 130ms to 70ms on my MacBook. This is more or less the diff I see when building your test site with this branch and the master branch.
• In the final setup we will also cache the comiled WASM files to disk (like we do for Katex) and, also, if you have the images cached to disk, it will be as fast as before.

[jmooring]

Other than a stray debug statement, this looks good to me.