target x86_64-unknown-linux-musl --manifest-path ./elk/Cargo.toml And then it would have no dynamic dependencies: $ ldd ./target/x86_64-unknown-linux-musl/release/elk statically linked $ file ./target/x86_64-unknown-linux-musl/release/elk ./target/x86_64-unknown-linux-musl/release/elk: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV

fn show(v: impl Display) { println!("{v}"); } $ cargo run --quiet C 64 But… it feels a little wrong to have to write all that code just to do that. Ah, that’s because you don’t! Dynamically-sized types Uhhh. What does any of that mean? Okay, so it’s more implementation details: just like bit widths (u32 vs u64), etc. But details are

version of React without the baggage. Two-way binding is magical when it works: just store dynamic properties within the data object, use the getter/setter methods (or built-into-JS accessors if you’re feeling adventurous and independent from all IE compatibility needs) and everything updates smoothly. However, Ractive proved very hard to debug

same way you do your business logic is fantastic. (Whereas in dynamic languages, the stack trace stops at OpenSSL). And that code takes full advantage of the lack of function coloring: it can let the runtime worry about non-blocking I/O and scheduling. But it comes at a terrible cost, too. There is excellent tooling out there for many things, which

Placeholder : 0 0.0%, 0.0% 0.0% 0.0% 0.0% Generator : 0 0.0%, 0.0% 0.0% 0.0% 0.0% GeneratorWitness : 0 0.0%, 0.0% 0.0% 0.0% 0.0% Dynamic : 0 0.0%, 0.0% 0.0% 0.0% 0.0% Closure : 0 0.0%, 0.0% 0.0% 0.0% 0.0% Tuple : 1 1.7

then send traces to something like the OpenTelemetry Collector, which could in turn be configured to forward those traces to Honeycomb, let’s not. There’s two main reasons: the first, is that I don’t like tying tracing and opentelemetry. I’ve had bad experiences in the past trying to dynamically filter the “tracing” end of things to

local name is not a &'static str, it’s a String. It’s been allocated dynamically, and it will be freed. Its lifetime is less than the whole program (even though it happens to be in main). To store a non-'static string in Person, it needs to either: A) Be generic over a lifetime: struct Person<'a> { name: &'a str, } fn main() { let name

Load = 0x1, Dynamic = 0x2, Interp = 0x3, Note = 0x4, } impl_parse_for_enum!(SegmentType, le_u32); We’ll only need one additional trick - just like we used derive-try-from-primitive for enums, we’ll use enumflags2 for bitflags for which each flag is an enum variant. $ cd delf/ $ cargo add [email protected] Adding enumflags2 v0.6

safety - it also talked about correctness. Well, it also talked about diversity and inclusion, which I think is also extremely important, but it’s not an intrinsic quality of the language, more of a state of affairs - which we cannot take for granted, as the nature of human dynamics is that they are… dynamic. Which is not to say that the

Forwarding server 54022] Got connection 0 [19:27:01.796] ------ [19:27:01.807] [Forwarding server 54022] Got connection 1 [19:27:01.809] Failed to set up socket for dynamic port forward to remote port 43703: connect ECONNREFUSED 127.0.0.1:54016. Is the remote port correct? [19:27:01.809] > local-server-1> ssh child died, shutting down [19:27:01.809