Crystal clear intro to the challenges of inlining with good debug info https://docs.google.com/presentation/d/1Wcblp3jpfeKwA0Y4FOmj63PW52M_qmNqlQkNaLj0P5o/edit#slide=id.p (even though Go lets you inspect the stack!)
miniblog.
Amusingly, *technology* book sales still prefer paper over ebooks!
If you've ever fancied implementing a type checker, there's a fun example in readable JS here: https://languagengine.co/blog/so-you-want-to-write-a-type-checker/
JIT compiling elisp: https://nullprogram.com/blog/2016/12/11/ (really nice demonstration of the power of lisp)
To my surprise, mapcar is so fast (it's an elisp primitive) that creating lambdas is cheaper than using a loop:
Intriguingly, Haskell has *three* exponentiation operators to ensure everything is type safe:
Let’s stop copying C https://eev.ee/blog/2016/12/01/lets-stop-copying-c/ (excellent overview of C's quirks and how it has influenced later languages)
I have graciously been given access to @ecotd, so do follow that account to learn new Emacs commands! (cl-incf productivity)
If git diff or git log shows you tons of added/deleted files, you can use --diff-filter to just see changed files!
Many of my python docstrings could be shorter with a Rust type system. I end up writing "mutates" or "returns copy" rather than &mut Foo.
Why does a Turing-complete type system make type checking undecidable? https://composition.al/blog/2017/02/27/why-does-a-turing-complete-type-system-make-type-checking-undecidable/ (Java's type checker is Turing complete!)
Google now supports searching for language syntax like === https://blog.google/products/search/improvements-searching-special-characters-programming-languages/ (handy for infix heavy PLs like Scala or Haskell)
I don't see any value in an Optional type with a dynamic type system. AFAICS you can only avoid NPEs with a static or gradual type checker.
Emacs C has lots of sizeof(struct)*CHAR_BITS. Explicit is good, but I doubt many users have CHAR_BITS != 8.
Showing 3,796-3,810 of 7,588 posts