home.social

Search

1000 results for “cpp”

  1. Day 9/75: Sliding window - fixed size

    Today's note was about using a stable invariant so sliding window - fixed size feels like a process instead of a trick. I kept coming back to the same checks: name the exact window, prefix, or pointer region each variable owns, reuse prior work instead of recomputing the same range each iteration, and test boundary sizes first because they expose weak invariants quickly.

    The failure mode worth watching is moving boundaries before stating what region they actually represent. If that happens, the implementation usually looks busy while the invariant is already gone.

    #CPP #DSA #Algorithms

  2. It took me a while (bc I'm lazy), but I finally integrated my test framework Icaro with my build system Dedalo (as it was intended to be from the beginning).

    It's still a bit awkward to set up, but `ddl test` successfully compiles and runs the tests placed in `tests/tests.cpp`.

    I'm sure there'll be a lot of bugs, but it's growing nicely.

    gitlab.com/ludusestars/dedalo

    #cpp #testing #tdd #handmade

  3. It took me a while (bc I'm lazy), but I finally integrated my test framework Icaro with my build system Dedalo (as it was intended to be from the beginning).

    It's still a bit awkward to set up, but `ddl test` successfully compiles and runs the tests placed in `tests/tests.cpp`.

    I'm sure there'll be a lot of bugs, but it's growing nicely.

    gitlab.com/ludusestars/dedalo

    #cpp #testing #tdd #handmade

  4. It took me a while (bc I'm lazy), but I finally integrated my test framework Icaro with my build system Dedalo (as it was intended to be from the beginning).

    It's still a bit awkward to set up, but `ddl test` successfully compiles and runs the tests placed in `tests/tests.cpp`.

    I'm sure there'll be a lot of bugs, but it's growing nicely.

    gitlab.com/ludusestars/dedalo

    #cpp #testing #tdd #handmade

  5. 🦀 How (and why) we rewrote our production C++ frontend infrastructure in Rust

    While memory-safe languages like Rust offer real benefits, serious cryptographic implementations inevitably rely on unsafe code, assembly, and low-level control, eroding those guarantees. At that point, the added abstraction often increases complexity without meaningfully reducing risk.

    blog.nearlyfreespeech.net/2026

    #cpp #rust #riir

  6. 🦀 How (and why) we rewrote our production C++ frontend infrastructure in Rust

    While memory-safe languages like Rust offer real benefits, serious cryptographic implementations inevitably rely on unsafe code, assembly, and low-level control, eroding those guarantees. At that point, the added abstraction often increases complexity without meaningfully reducing risk.

    blog.nearlyfreespeech.net/2026

    #cpp #rust #riir

  7. 🦀 How (and why) we rewrote our production C++ frontend infrastructure in Rust

    While memory-safe languages like Rust offer real benefits, serious cryptographic implementations inevitably rely on unsafe code, assembly, and low-level control, eroding those guarantees. At that point, the added abstraction often increases complexity without meaningfully reducing risk.

    blog.nearlyfreespeech.net/2026

    #cpp #rust #riir

  8. 🦀 How (and why) we rewrote our production C++ frontend infrastructure in Rust

    While memory-safe languages like Rust offer real benefits, serious cryptographic implementations inevitably rely on unsafe code, assembly, and low-level control, eroding those guarantees. At that point, the added abstraction often increases complexity without meaningfully reducing risk.

    blog.nearlyfreespeech.net/2026

    #cpp #rust #riir

  9. @glloyd It crops up in other places, not just iterators. I first encountered it using a coroutine library where the promise type was a std::expected. I did the usual “how am I being stupid” for a while before I figured it wasn’t me (for once). #cpp #cplusplus #clang #cpp26

  10. @glloyd It crops up in other places, not just iterators. I first encountered it using a coroutine library where the promise type was a std::expected. I did the usual “how am I being stupid” for a while before I figured it wasn’t me (for once).

  11. @glloyd It crops up in other places, not just iterators. I first encountered it using a coroutine library where the promise type was a std::expected. I did the usual “how am I being stupid” for a while before I figured it wasn’t me (for once). #cpp #cplusplus #clang #cpp26

  12. @glloyd It crops up in other places, not just iterators. I first encountered it using a coroutine library where the promise type was a std::expected. I did the usual “how am I being stupid” for a while before I figured it wasn’t me (for once). #cpp #cplusplus #clang #cpp26

  13. @glloyd It crops up in other places, not just iterators. I first encountered it using a coroutine library where the promise type was a std::expected. I did the usual “how am I being stupid” for a while before I figured it wasn’t me (for once). #cpp #cplusplus #clang #cpp26