Cracking the Shell

As I mentioned in my previous post, I started a Google Summer of Code project to (more or less) dig tests/debuginfo out of tech debt.

Since my last post, my work regarding Rust debugging as slowed a bit.

I'm a big fan of eink tablets.

In my previous post, I described implementing PDB parsing as a can of worms.

Well, it's "done".

Let me start with an emphatic "me too".

Lets say you want to store two different types of objects in 1 container.

Seriously, is there a good reason for this?

Partial borrows across function boundaries don't really work in Rust.

Oh how naive I was when I thought I'd be moving on to pathfinding and abilities.

A while back, I made a small application meant to demonstrate some important principles about RTS design, namely that unit stats in a vacuum can be very misleading.

I encountered a neat example recently while solving Advent of Code 2015, day 6.

To keep the preamble brief, I did a bunch of digging and analysis a year or two ago and never did anything with the data.

I've seen this question come up a few times on r/ssbm and while I've given hand-wavey answers before, I find myself in a good place to answer more rigorously now.

I write my own sublime-syntax files for the syntax highlighting on this site, this page is meant for testing edge cases.