You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In rustls-ffi, we are hoping to export some ciphersuites (rustls::SupportedCipherSuite structs) to C code, by putting them in a const array (see rustls/rustls-ffi#165). One obstacle we are running into is that each rustls::SupportedCipherSuite has several statics inside of it, and you can't declare a const that points to statics:
I am not a Rust expert, but from my understanding, the Rust compiler has gotten smarter about its ability to evaluate consts, which may make the conversion from static to const possible now, especially if your compatibility guarantee is only for the latest stable version of Rust.
If there is otherwise no difference, would it be possible to change some of the static values in ring to const values instead?
I will take a shot at a patch to see if it's technically feasible, then we can go from there.
The text was updated successfully, but these errors were encountered:
In rustls-ffi, we are hoping to export some ciphersuites (
rustls::SupportedCipherSuite
structs) to C code, by putting them in a const array (see rustls/rustls-ffi#165). One obstacle we are running into is that eachrustls::SupportedCipherSuite
has several statics inside of it, and you can't declare a const that points to statics:I am not a Rust expert, but from my understanding, the Rust compiler has gotten smarter about its ability to evaluate consts, which may make the conversion from static to const possible now, especially if your compatibility guarantee is only for the latest stable version of Rust.
If there is otherwise no difference, would it be possible to change some of the
static
values in ring toconst
values instead?I will take a shot at a patch to see if it's technically feasible, then we can go from there.
The text was updated successfully, but these errors were encountered: