A sign of a well written test suite is when new users reporting bugs can see how to write a failing test.
miniblog.
Rather than showing compiler errors in a different window to your editor, BSD has long been able to annotate code! https://lambda-the-ultimate.org/node/5280#comment-90779
Really interesting blog post describing a case where GCC developers decided to not exploit undefined behaviour:
Is Sound Gradual Typing Dead? https://www.ccs.neu.edu/racket/pubs/popl16-tfgnvf.pdf (explores the significant performance cost of partially specified types in Racket)
Great introduction to omniscient debugging, including comments on keeping performance acceptable: https://www.drdobbs.com/tools/omniscient-debugging/184406101
Brilliant deep dive on the Midori compiler, and its quest for performant, safe, GC'd language implementation:
Common misconceptions of orthogonal persistence: https://tunes.org/wiki/orthogonal_20persistence.html
Joe Duffy has a fascinating blog post on efficient asynchronous API design for systems:
A Persistent System in Real Use - Experiences of the First 13 Years https://tunes.org/wiki/eumel.html (amazing OS where even processes are persistent)
Good compiler error messages are hard. LtU: https://lambda-the-ultimate.org/node/5280#comment-90836 if two parts of a function use different types, what do you highlight?
Refactored some unsafe FFI code to be idiomatic Rust today, and valgrind approves of everything on the first run. I'm impressed!
TIL that Go has an excellent CLI tool for renaming things: https://texlution.com/post/gorename/ -- why doesn't this exist in more languages?
"The less often you run a script, the chattier the interface should be."
Lenticular editing is an interesting idea where doc changes are replayed as code comments (and vice versa). https://www.russet.org.uk/blog/3035
Showing 4,846-4,860 of 7,549 posts