docs: clarify freeing client/server builder directly #443
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously the docs for the
rustls_client_config_builder
andrustls_server_config_builder
structs seemed to imply the only safe way to dispose of a builder was to build it, and then free the resulting config (e.g. this is a pattern curl uses for its rustls-ffi integration ). It's also possible (and clearer for most error-handling paths) to free the builder directly.This commit updates the relevant docs to make this alternative option clearer.