Lu Pan

A really cool small piece of integer division code in `folly::BucketedTimeSeries` – uvdn7.github.io/bucketed-time-….

I wrote this post on the mental model for C++ coro in March, and found myself referring back to it often. Let me just post it uvdn7.github.io/cpp-coro/.

Guice configuration is like makefile, and injection is like dynamic linking, but all in Java.

Say there are 100 doors with 98 regular goats, 1 special goat and 1 car. You pick on door, then the host opens 98 doors with 98 goats behind them. These 98 goats happen to be all regular goats. Would you switch the door to maximize the probability of getting the special goat?

OK I have my answer – I think you should switch.

[new blog post] Access a function's return value in C++ scope guard blog.the-pans.com/return-value-s…

[new blog post] When `__cxa_pure_virtual` is just a different flavor of SEGFAULT blog.the-pans.com/pure_virtual/

The gnu bash manual is great. It's well-structured and concise. Just wonderful. Lots of effort must went into it. gnu.org/software/bash/…

The list of talks of NEDB Day 2024 is out! #papers" target="_blank" rel="nofollow noopener">bu-disc.github.io/nedbday/2024/#… I saw "Why Machine Learning for Automatically Optimizing Databases Doesn't Work" and was thinking Andy Pavlo would have something to say about it, then I realized that he's the one giving the talk! #NEDBDAY2024

Not only the book Infinite Powers is fascinating (and I can’t put it down), I can feel @stevenstrogatz’s passion and love of the subject from the pages. The book is a wonderful gift. I am grateful.

`async && closure && requires_explicit_memory_management && !borrow_checker` is really challenging. Borrow checker is really good to have especially when writing async code with closure! #rust

[new blog post] Rust's early vs. late lifetime binding blog.the-pans.com/rusts-early-vs…

users.rust-lang.org/t/capture-the-… is the answer. The actual capture algorithm is described here github.com/.../closure-do…...

It does indeed compile in the playground play.rust-lang.org/?version=stabl…. But it doesn't on Compiler Explorer (godbolt.org/z/WjozhxGoW), or on my local machine. All tested on version 1.76.

It appears that the rust compiler tries really hard to infer how _and_ what to capture when it comes to closures. Do you think the following program compiles? #rust

@iavins @MarkCallaghanDB is your guy

I would like to understand write-amplification in B Tree vs LSM Tree. Is there any survey/research paper explaining the same? or a blog post? I found a few articles online, but none covered all the aspects and missed nuance. e.g. batching in LSM tree, WAL in B tree etc.

Why a standalone redirect e.g. `2>/dev/null` gets interpreted as a `cat` command in zsh? The consequence is that then the shell will wait for the cat command which is waiting on stdin ... bash simply does nothing in this case.

It looks like every value expression in rust behaves like xvalue in C++ – it has (or can have) an identity (so it can be borrowed) and can be moved from.

`getcontext/setcontext` are not system calls but why there are getcontext(2)/setcontext(2) entries man7.org/linux/man-page…? `man getcontext.2` also exists although it shows the content for getcontext(3).

If the function is declared extern, then this definition of the function is used only for inlining. In no case is the function compiled as a standalone function, not even if you take its address explicitly. gcc.gnu.org/onlinedocs/gcc…

@davidtgoldblatt helped me! It is because of the __gnu__inline__ attribute which changed the behavior.

How come gcc has `extern inline` with inline definition in the header without running into ODR (xmmintrin.h)?