miniblog.

Thinking more about the "auto eval definitions" approach, I think it breaks down when debugging. If I want to step through the existing definition, it'd be really awkward to re-evaluate the definition at my cursor.

"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.

One striking downside of string interpolation is that accurate syntax highlighting becomes much harder. It's very easy to add some form of nesting, which breaks the "simple lexer" approach to highlighting.