moonbitlang / async / 634

77%

Build Type

push

github

Committed by web-flow

Commit Message

tls: load OpenSSL lazily on first TLS use, not at startup (#453)

* tls: load OpenSSL lazily on first TLS use, not at startup

Load libssl (dlopen + ~50 dlsym) and build the shared client/server SSL_CTX
lazily on first use, not at process startup, so a program that links this
package but never touches TLS pays nothing before main. A single guarded
load_openssl() does the loading + BIO method setup, the shared contexts are
memoized in Ref[SSL_CTX?] cells, and every raw-symbol FFI wrapper
(SSL_CTX::client/server, create_bio, rand_bytes, sha1) calls it first so
standalone crypto entry points like @tls.rand_bytes / @tls.sha1 still load
correctly without a TLS connection.

* tls: raise instead of abort on OpenSSL load failure, cache the outcome

Now that OpenSSL is loaded lazily on first TLS use rather than at startup,
a load failure can be reported as a recoverable error instead of killing the
program. Turn every `abort` in `load_openssl` and the SSL context init into
`raise TlsError`, and propagate `raise` up the call chain (SSL_CTX::client/
server, client_ctx/server_ctx, create_bio, from_pair, sha1).

`openssl_loaded` becomes `Result[Unit, Error]?` so a failed load is cached and
re-raised immediately on subsequent calls instead of retrying every time.

Addresses review feedback on #453.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

* tls: simplify cached-outcome handling with Result::unwrap_or_error

Replace the two explicit `match`es in `load_openssl` (cached-outcome check and
post-attempt re-raise) with `Result::unwrap_or_error`.

---------

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Coverage Stats

29 of 36 new or added lines in 3 files covered. (80.56%)

2 existing lines in 2 files now uncovered.

3590 of 4657 relevant lines covered (77.09%)

72436.03 hits per line