How protonuorecall/xeno-source-code works
There is no README or demonstrated application-level wiring. The sampled sources show independent request handlers, channel workers, and native utility code; the tree alone does not establish a shared product workflow. The graph captures only behaviors visible in the excerpts, so it does not infer connections among these modules.
Main entry points: setup_48.rs Async handlers · cache.go Cache workers · helpers.go Helper workers
Components 10
Request handling
- Async handlers
drivers/usb/modules/setup_48.rs
Channel workers
- Cache workers
handlers/cache.go - Helper workers
handlers/helpers.go
Native utilities
- Native compute
lib/x64/utils/handler.c - Renderer compute
src/renderer/lib/x64/init_17.c - Cache API utilities
modules/cache/src/renderer/api.c - Middleware utilities
utils/middleware_14.c
Other components
- Request caller
- Channel producer
- Standard output
Connections 6
- Request caller → Async handlers: sends request
- Async handlers → Request caller: returns length
- Channel producer → Cache workers: sends values
- Channel producer → Helper workers: sends values
- Cache workers → Standard output: prints results
- Helper workers → Standard output: prints results