[HN Gopher] My Kind of REPL
       ___________________________________________________________________
        
       My Kind of REPL
        
       Author : ianthehenry
       Score  : 53 points
       Date   : 2023-07-05 14:03 UTC (1 days ago)
        
 (HTM) web link (ianthehenry.com)
 (TXT) w3m dump (ianthehenry.com)
        
       | edrx wrote:
       | 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! =)
        
         | abecedarius wrote:
         | While we're at this: https://github.com/darius/halp -- I came
         | up with it 16 years ago and still use it.
         | 
         | Example of use: the ## comments and #. outputs in
         | https://github.com/darius/sturm/blob/master/tictactoe.py#L20...
         | 
         | (It'll need a Python 3 update if you're more up with the times
         | than me.)
        
       | gjvc wrote:
       | _I mean that you can write programs that edit their own source
       | code._
       | 
       | Like smalltalk.
        
       | giraffe_lady wrote:
       | 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.
        
       | LectronPusher wrote:
       | 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?
        
         | ianthehenry wrote:
         | Mutation testing is where you make changes to your code's logic
         | as a way to ensure that you have good test coverage for that
         | bit of logic. Mutation testing is helpful with any _kind_ of
         | tests -- assertions, snapshots, whatever -- as a way to check
         | that your tests are actually able to catch interesting bugs,
         | but the idea is orthogonal to this workflow.
        
       ___________________________________________________________________
       (page generated 2023-07-06 23:03 UTC)