remoting API
- Lenguaje dominante
- Rust
- Estrellas
- 2.3k
- Forks
- 230
- Merge medio
- 3 d 12 h
- PR fusionados (30 d)
- 38
Descripción
As the popularity of bootc grows a central location for go types/examples would be useful for projects. Speaking with @cgwalters he is willing to consider something similar to rpmostree-client-go[1] for bootc but there is some intersection with [2].
Curious if instead of creating go client as a os exec wrapper, exposing some of the Rust functionality via CGO? Please include me in future conversations on the topic if possible :pray: Wasmtime CGO examples as ref. [3],[4]. I understand that CGO is not ideal but in terms of interaction with Rust over FFI, I don't believe there is another option.
[1] https://github.com/coreos/rpmostree-client-go/
[2] https://github.com/containers/bootc/issues/518
[3] https://github.com/bytecodealliance/wasmtime/blob/b869b66bce8a57c9e83db4e3bcd6809d88e94a5f/crates/c-api/src/types/extern.rs#L39
[4] https://github.com/bytecodealliance/wasmtime-go/blob/cabc733f95623fb897b2c35266124192ffca94b4/externtype.go#L9C12-L9C29
Guía de contribución
Línea de trabajo
Start by reading the related bootc issue #518, then compare rpmostree-client-go with the linked Wasmtime C API and Go examples. The issue needs a settled scope for a central Go API, including whether it should wrap os execution or expose Rust functionality through CGO; completion is an agreed approach and defined API/examples.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- go, rust
- Área
- api, backend-api-design
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100