Do compilers ever transform pairs of malloc/free? E.g. in a loop:
p = malloc(32);
foo(p);
free(p);
In principle this doesn't need to be allocated on the heap.
miniblog.
I'm writing ASCII diagrams for docs. It's not terribly pretty, but it's so easy to contribute to.
I've seen so many beautiful architecture diagrams go stale because no-one wants to find the file and the GUI tool to keep it updated.
mdbook is a popular tool for Rust projects to document how they work: https://github.com/rust-lang/mdBook/
I suspect the name really helps: "writing a book" sounds much more impressive than "writing some docs"!
Neat GitHub bot that uses ML to infer whether a task is a bug, a feature request or a question: https://github.com/marketplace/issue-label-bot
The bot is no longer available as a service, but the source is available: https://github.com/machine-learning-apps/Issue-Label-Bot
Superb deep dive on rust compile optimisation with CI caching, examining usage of monomorphisation, and graphing the build tree: https://matklad.github.io/2021/09/04/fast-rust-builds.html
Adding a new language to difftastic is straightforward, but it requires some configuration and testing.
I just started with languages I've recently used. I'm trying to be more quantitative and use GitHub data: https://madnight.github.io/githut/
What languages would you like to see?
I'm delighted to announce difftastic 0.8! In this release:
* tree-sitter parsers are much improved and now the default
* added support for Python and Java
* better handling of added/removed files
"When your Rust code breaks, look at unsafe blocks."
I initially parsed this as "consider adding unsafe blocks"! Turns out they meant "crashes are more likely to be caused by existing unsafe blocks". Phew.
Applying PGO to rustc (on both LLVM and the Rust-based frontend) can provide a ~10% improvement to compile time! https://blog.rust-lang.org/inside-rust/2020/11/11/exploring-pgo-for-the-rust-compiler.html
This has been recently merged to Rust's CI: https://github.com/rust-lang/rust/pull/88069
Taking a break from debugging graph traversal algorithms to give difftastic a logo :)
One problem with syntactic-based diff tools (like difftastic) is that they can show confusing results when replacing a function.
I've realised that traditional diffs have the same problem! There's one common line between old and new, and diff has matched the closing parens.
Why swap is still relevant on modern systems, regardless of the amount of RAM available: https://chrisdown.name/2018/01/02/in-defence-of-swap.html
earlyoom is a neat linux tool that kills processes a little earlier, so your system remains responsive: https://github.com/rfjakob/earlyoom
The readme is pretty educational too, and even encourages you to `tail /dev/zero` to see it in action!
Based on job ads, Apple is already designing devices with RISC-V components! https://www.tomshardware.com/news/apple-looking-for-risc-v-programmers
Write a single cross-platform app or do native development on each platform? The ability to ship the same features everywhere without team co-ordination is a major win: https://allenpike.com/2021/gravity-of-cross-platform-apps
The next release of difftastic should have Python support!
The screenshot doesn't look terribly impressive, but it's showing that difftastic now understands that whitespace is meaningful in Python. Tree-sitter has a pre-existing Python parser we can use :)
rust-analyzer is experimenting with a really clever feature: allow types to open a link to their external docs! https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/dev/lsp-extensions.md#open-external-documentation
I've definitely thought about referencing external resources from an editor: in principle you could even fetch the first paragraph inline too!
Fun post looking at an impressive transformation in clang and tracing it through the different optimisation passes:
https://blog.matthieud.me/2020/exploring-clang-llvm-optimization-on-programming-horror/
Meta-FizzBuzz: Implement a sufficiently complete programming language that you can write FizzBuzz in it! https://www.moserware.com/2008/08/meta-fizzbuzz.html
I've added some new keybindings to deadgrep.el, so I split the shortcut tables into two categories: https://github.com/Wilfred/deadgrep#keybindings
I've done this purely by intuition. Are there good rules or heuristics for deciding when more hierarchy is needed in information, I wonder?
Showing 101-120 of 345 posts