Programming language implementation work seems to be 10% interesting semantic work and 90% error checking against the possible malformed programs you might encounter.
miniblog.
Related Posts
@tristanC That's an option! There's often cases where you know what the user wanted though, so you can provide a sensible AST that the toolchain can handle.
For example, a malformed string literal can still be parsed a string so type checking etc can be helpful.
Rust's backtraces moving to be native Rust: https://github.com/rust-lang/rust/pull/74682/commits/06d565c967bfb7c6ff52a991bbe47b4a2a25de3e
This prevents malformed DWARF info leading to security issues, an avenue for vulnerabilities I'd not considered before. https://twitter.com/Brittain_Ben/status/1288193388588740615
@kennethreitz It would be wonderful if http://t.co/OA43LXO4 could return a malformed HTTP response for testing `httplib.BadStatusLine`. :)