The GCC wiki has a scary list of all the arithmetic transformations that don't work in compliant floating point C:
miniblog.
When programming python, I miss the ability to advise functions. Decorators are like around-advice, but often after-advice is sufficient.
If you ever force push with git, you should really use --force-with-lease to avoid accidental clobbering. If you use magit, it's automatic!
On the inefficiency of computer UIs for information display:
Emacs package of the day: emacs-rustfmt: https://github.com/fbergroth/emacs-rustfmt . Automatically formatting code on save is a revelation.
BF interpreter written in Hodor written in Rust macros: https://www.reddit.com/r/rust/comments/39wvrm/hodor_esolang_as_a_rust_macro/cs76rqk (source code is a treat to read)
Fantastic overview of the Rust compilation process, with a walkthrough of the source code:
How to design a good API for autocompletion, based on experience with YouCompleteMe:
Fascinating design rationale for Rust's crate system: allow circular dependencies but only within a project:
Nifty: using ud2 (the official 'undefined instruction opcode' on x86) for self-modifying code in the Linux kernel:
Interesting paper on assessing API usability based on the questions developers ask on Stack Overflow: https://www.cs.cmu.edu/~aldrich/papers/icpc15-searching.pdf
Having an interpreter and compiler allows interesting workflows. E.g elisp users can try in the interpreter then compile when they're happy.
Emacs command of the day: kmacro-name-last-macro. Concocted a great macro? Save your last macro as a named command for later use.
Showing 4,936-4,950 of 7,583 posts