miniblog.

← Back to all posts
Jul 22, 2017 at 23:34
An elegant way of seeing if you're breaking API compatibility: try building all the downstream deps against WIP!
GitHub - brson/cargo-crusader: Test the downstream impact of Rust crate changes before publishing
GitHub - brson/cargo-crusader: Test the downstream impact of Rust crate changes before publishing
Test the downstream impact of Rust crate changes before publishing - brson/cargo-crusader

Related Posts

Dec 9, 2024 at 00:01
I've been building an 'extract function' refactor feature. It's surprisingly nuanced. Where do you put the extracted function? Once you've done the static analysis, what order do you use for the parameters?
Aug 10, 2024 at 23:21
Today I learnt that Emacs 28 shipped a context-menu-mode! https://oylenshpeegul.gitlab.io/blog/posts/20230129/ This seems quintessentially Emacs: deeply hackable, but building UI features in an order very different to the mainstream.
Context menus in Emacs 28!
Today I learned that Emacs 28 added context-menu-mode so that we can easily add context menus. This is a minor mode which you can toggle with M-x context-menu-mode RET but I added hooks to enable it for text mode and a couple others (add-hook 'text-mode-hook 'context-menu-mode) (add-hook 'shell-mode-hook 'context-menu-mode) (add-hook 'dired-mode-hook 'context-menu-mode) I did not hook prog mode because some of the fancier lsp things already use mouse-3.
Jul 5, 2024 at 22:58
A funny side effect of building software in Rust: my machine OOMs much more during development. I'm not entirely sure why. I think Rust makes it easy to allocate data quickly, and sooner or later you write an infinite loop when coding.