miniblog.

← Back to all posts
Jan 21, 2023 at 20:48
Defining a separate tests module so rust tests compile faster:
Delete Cargo Integration Tests
Click bait title! We'll actually look into how integration and unit tests are implemented in Cargo. A few guidelines for organizing test suites in large Cargo projects naturally arise out of these implementation differences. And, yes, one of those guidelines will turn out to be: delete all integration tests but one.

Related Posts

Jan 13, 2023 at 08:40
What's your preferred granularity of docs? (a) A whole module on one page, e.g. https://pkg.go.dev/time, making search easy? (b) A function per page, e.g. https://www.php.net/manual/en/function.time.php, giving more space for examples and See Also sections? I'm torn, and I've seen both done well.
time package - time - Go Packages
Package time provides functionality for measuring and displaying time.
PHP: time - Manual
PHP: time - Manual
Return current Unix timestamp
Nov 25, 2020 at 07:45
PL module systems impacting IDE design, and how salsa (Rust memoisation library for trees of function calls) is used in rust-analyzer:
Three Architectures for a Responsive IDE
rust-analyzer is a new
Sep 20, 2020 at 01:33
I really like the one-module-per-file model of JavaScript or Python. If you're storing code in files, you might as well leverage file boundaries. If modules are a separate abstraction (e.g Rust, OCaml), it's harder to learn and choose how to organise code.