Yeah I didn't mean a one-to-one implementation in the pedantic sense; I meant more like how it would be implemented to address certain issues in C++ that I demonstrated at the beginning. Sorry if I wasn't clear with the article.

Thanks for letting me know, I will update the article!

You can combine this with Nixhub to find the precise commit of nixpkgs, if you need a copy of stable for a specific package! For example, I needed to get draw.io before it changed its license to a non-FOSS, so I pinned it to a specific commit hash.

The commit hash goes in the configuration like this (example): nixpkgs-lvm.url = "github:nixos/nixpkgs/2fbfb1d73d239d2402a8fe03963e37aab15abe8b";

This is the first article that I write of this type, so I tried to create a balance between implementation and explanation without making the latter strictly dominate the pacing. If anyone has feedback I'd appreciate!