Spent a bit longer between devlogs this time, but it was worth it.
So I realized the error messages were really bad. I was pretty much just passing errors up the call stack without adding any context, which isn’t great since it means our error messages will be useless to people reading them
I therefore went through every single file of the codebase and wrote good error messages which add a bit of context every time we pass it up the call stack.
I also did a bit of refactoring where I thought it would be worth it. For example in the shim module I now set the PE subsystem of the shim binary while it’s in memory instead of writing to disk twice.
A few good examples of what the new error messages look like can be seen in the video below.
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.