nmwsharp / nmwsharp/polyscope

Rust Version

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

Nobody has claimed this yet.

Dominant language
C++
Stars
2.2k
Forks
242
Avg merge
11m
Merged PRs (30d)
1

Description

Hi there,

There was an issue about rust wrapper several years ago:
https://github.com/nmwsharp/polyscope/issues/127

But it seems paused/stopped since 0.2.1 and many features are not complete.

As a part of my own experiment for testing how far AI-driven can go and if it can manage mid-scale software development, I did a rust-native version of polyscope here over the past 2 weeks.
https://github.com/xarthurx/polyscope-rs

I would say it is now in a relative feature-complete status and will need some test from the Rust community.
But before publishing it to the crates.io ecosystem, are you fine with the names? or do you prefer it to be different from polyscope?

Thanks.
Feedback and comments are welcome.

@nmwsharp

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.

Research direction

Start by reviewing the earlier Rust-wrapper issue #127 and the linked external polyscope-rs project. The issue asks for maintainer feedback on feature completeness and names before publishing to crates.io, but it identifies no repository files, tests, or concrete implementation task; completion would require a maintainer decision.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.