0xPlaygrounds / 0xPlaygrounds/rig

refactor: split rig providers into own crate

Aperta
#741 1 commento 1 reazione 0 assegnatari Vedi su GitHub
feat
Lingua principale
Rust
Stelle
8.6k
Fork
959
Merge medio
4h 32m
PR unite (30g)
117

Descrizione

- [x] I have looked for existing issues (including closed) about this

## Feature Request

The title is self explanatory.

### Motivation

The rationale behind this is that if we split the providers into its own crate, users are then able to essentially use whatever providers they want without anything else.

I think this is important because it does seem that Rust is missing a good crate just for calling LLMs.

### Proposal

Split the `rig::providers` module into its own crate. That's pretty much it.

### Additional
I will be assigning this work to myself as this is a very large change with sweeping implications if this gets accepted.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

The providers module is currently in rig::providers. Examine its structure, dependencies, and how it's used throughout the codebase. The goal is to extract it into a separate crate, which involves updating Cargo.toml, managing public/private APIs, and ensuring downstream usage remains compatible. Start by reviewing the existing module and its integration points.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
rust
Ambito
backend-api-design, tooling
Tipo di issue
Refactoring
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.