x509 ของ golang support ed25519 แล้วนะ
โคตร type signature วันนี้
Map<std::slice::Iter<'_, types::contract_event::ContractEvent>, std::result::Result<(std::string::String, std::string::String, std::string::String, u64), failure::Error>, [[email protected]/xxx/yyy.rs:53:9: 60:10]
Are you telling me that Rust apps won’t even work with stable releases of the language? How is this acceptable?
error[E0554]: #![feature] may not be used on the stable release channel --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/pear_codegen-0.1.2/src/lib.rs:1:1 | 1 | #![feature(crate_visibility_modifier)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error[E0554]: #![feature] may not be used on the stable release channel --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/pear_codegen-0.1.2/src/lib.rs:2:1 | 2 | #![feature(proc_macro_diagnostic, proc_macro_span)] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error: aborting due to 2 previous errors For more information about this error, try `rustc --explain E0554`. The following warnings were emitted during compilation: warning: Pear was unable to check rustc compatibility. warning: Build may fail due to incompatible rustc version.
“Heh, well we solved the memory safety problems but you’ll never know which version of of the mime type library is actually in the fast path if there’s every a vulnerability”
Compiling mime_guess v2.0.0-alpha.6 Compiling mime_guess v1.8.7
“Base64 is so complicated we have made dozens of crates for it. Of course they’re not ABI compatible, so we need both.”
Compiling base64 v0.10.1 Compiling base64 v0.9.3
In case you’re wondering here’s the entire list of dependencies sorted so you can see the duplicates
Now I’d like someone to explain why there’s openssl and rustls and nativetls and hyper-tls all in the same app toolchain. Is the community drunk? Can nobody decide on a canonical TLS library for this fancy new language? How many CVEs are lurking in this cesspool?
Compiling rand v0.4.6 Compiling rand v0.6.5 Compiling rand v0.7.0 Compiling rand_chacha v0.1.1 Compiling rand_chacha v0.2.1 Compiling rand_core v0.3.1 Compiling rand_core v0.4.0 Compiling rand_core v0.5.0
This is scary. Is something linking to an older random implementation that’s not so random?
Compiling sha-1 v0.3.4 Compiling sha-1 v0.8.1
Seems to be taking rust folks a while to figure out how to make a stable sha-1 implementation
(I joke, but it really annoys me how #Rust is still known as a blockchain language. We need some killer feature that spreads Rust farther.)
Jezen/is-thirteen: Check if a number is equal to 13 - https://github.com/jezen/is-thirteen