0xPlaygrounds / 0xPlaygrounds/rig

refactor: split rig providers into own crate

Abierto
#741 1 comentario 1 reacción 0 asignados Ver en GitHub
feat
Lenguaje dominante
Rust
Estrellas
8.6k
Forks
959
Merge medio
4 h 32 min
PR fusionados (30 d)
117

Descripción

- [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.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
rust
Área
backend-api-design, tooling
Tipo de issue
Refactorización
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.