Security issue notifications
N/A
Problem:
The automatic dependency update strategy makes it difficult for consumers who also use the same crate(s). This is evidenced by: cf77e2b
Need By Date:
N/A, this is a testing issue, but its a bit of a current pain point.
Solution:
Could s2n-quic-platform instead pin a low version and minimize public type exposure? This crate may not even need to expose turmoil types at all.
turmoil = { version = ">=0.6", ... }
I'd be happy to submit a PR if this approach is acceptable.
Security issue notifications
N/A
Problem:
The automatic dependency update strategy makes it difficult for consumers who also use the same crate(s). This is evidenced by: cf77e2b
Need By Date:
N/A, this is a testing issue, but its a bit of a current pain point.
Solution:
Could s2n-quic-platform instead pin a low version and minimize public type exposure? This crate may not even need to expose turmoil types at all.
I'd be happy to submit a PR if this approach is acceptable.