Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add manual `wgpu` API

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
computer-graphics

Research direction

No files, tests, or entry points are named. Start by tracing how libprocessing currently creates and exposes its Bevy and wgpu-native instances, then review the expected wgpu-native version and handle-sharing boundary. Done means the manual wgpu API and instance-sharing behavior are defined and implemented without requiring users to create a separate instance.

Written by the indexing model from the issue text.

Description

This will require some changes to how wgpu-native works, namely we'll definitely want to be able to return Bevy's instance rather than requiring users to create a new instance themselves. libprocessing will need to ship with a defined version of wgpu-native that users will be expected to interact with if they want to share wgpu handles between libprocessing and their custom WebGPU code. There's a ton of trickiness here and this will likely be a pretty difficult task.

Dominant language
Rust
Stars
69
Forks
14
Avg merge
15d 22h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from processing/libprocessing

All issues in processing/libprocessing

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.