MaxOhn / MaxOhn/rosu

use feature-flag to combine both crates under one

Open
#5 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Description

you could use a feature flag, so that the user chooses if they want to use v1 or v2 and all the code would be under the same crate

heck, you can still have 2 crates, that won't be publicly accessible, and have the main crate export either v1 or v2 based on the feature flag
(super easy to do with a cargo workspace)

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

Review the current crate layout and Cargo workspace configuration, focusing on how the v1 and v2 implementations are exposed. Determine the intended feature names and selection behavior, then verify that the chosen API is available through one public crate while the alternate crates remain internal.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.