I mean that you can write programs that edit their own source code.
Like smalltalk.
This is cool, I'm going to start trying it. I noticed elixir's doctests a few weeks ago and it seems like a partially related idea. It's not quite the same thing but I could see a formalization like them being the "other half" of the blog post's approach for a team.
This is great, especially the more graphic tests, and timely as I'm enjoying learning Janet.
This works for regression tests, and documentation, but not so much for something like TDD, where the test is more like (or should be) a specification for the program you are about to write.
Dude you are living in the matrix - in the best way possible. I love your post!
Is this not a form of mutation testing? With the added idea of treating anything you write to sanity-check the output as a test?
Has anyone ported this workflow to Common Lisp yet?
Hey: MANY, MANY, MANY THANKS!!!
I use REPLs in ways that are similar to yours, but 1) you have several tricks that are new to me, and 2) you've been able to put into words many ideas that I haven't!
My way is here,
http://anggtwu.net/eepitch.html
and I'm certainly going to cite you in my presentation in the next EmacsConf! =)