Switch Masyu Chrome Extension to C# WASM Solver#75
Switch Masyu Chrome Extension to C# WASM Solver#75google-labs-jules[bot] wants to merge 3 commits intodotnetfrom
Conversation
- Remove Pyodide-based `solver.py` and logic. - Add `DotNet/MasyuSolver` project implementing Masyu logic in pure C#. - Configure `MasyuSolver.csproj` for browser-wasm target. - Update `manifest.json` and `popup.js` to use `dotnet.js` and WASM artifacts.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
Qodana Community for Python125 new problems were found
☁️ View the detailed Qodana report Contact Qodana teamContact us at qodana-support@jetbrains.com
|
|
Use or-tools-tools. It's wasm compatible |
Thank you for the suggestion. I've investigated the possibility of using OR-Tools with WebAssembly. While Google OR-Tools is an excellent library, its current official .NET wrapper relies on native C++ libraries (p/invoke) that are not natively compatible with the browser-wasm runtime environment without significant and complex custom compilation (e.g. compiling the C++ core to WASM and linking it). Given the constraints of a simple Chrome Extension and the desire for a maintainable, lightweight solution, I have implemented a pure C# backtracking solver. This approach ensures full compatibility with the .NET WASM runtime (dotnet.js) out of the box and keeps the extension size efficient. |
- Implemented correct 'turn at neighbor' constraints for White circles in `MasyuSolver.cs` - Added robust `VerifySolution` method to ensure final solution validity. - Addressed PR feedback regarding OR-Tools usage (opted for pure C# due to WASM constraints).
- Removed Python and C# solver implementations. - Added Z3 WASM binaries (`z3-built.js`, `z3-built.wasm`). - Implemented `solver.js` using low-level Z3 C-API bindings (Emscripten). - Updated `manifest.json` and `popup.js` to integrate the new solver.
1 participant
Replaces the Python Masyu solver in the Chrome Extension with a C# implementation compiled to WebAssembly. The new solver uses a pure C# backtracking approach to ensure compatibility with standard .NET WASM runtimes (avoiding OrTools dependency issues). Updates the extension manifest and popup script to load the .NET runtime and invoke the solver via JS interop.
PR created automatically by Jules for task 2332407486224625241 started by @newtomsoft