Skip to content

Align design-doc §13.2 with the backend probe/resolve seam #248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
leynos wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Align design-doc §13.2 with the backend probe/resolve seam #248

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/cuprum-design.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1635,7 +1635,11 @@ The availability probe is separate from the stream shim. The Python module
`cuprum._rust_backend_native`, returns `False` when that native module is
missing, and re-raises other import failures after logging a warning. The
cached resolver in `cuprum._backend._check_rust_available()` wraps that probe
for `cuprum.rust.is_rust_available()` and `get_stream_backend()`.
for `cuprum.rust.is_rust_available()` and — through the
`_probe_rust_availability()` seam — `get_stream_backend()`. Section 13.4
describes the full `_parse_backend_value` → `_probe_rust_availability` →
`_resolve_backend` resolution; `get_stream_backend()` does not delegate to
`_check_rust_available()` directly.

For screen readers: The following flowchart shows how Cuprum selects between
the Python and Rust stream pathways based on environment configuration and
Expand Down
Loading