[HN Gopher] Creatively Misusing TLA+
       ___________________________________________________________________
        
       Creatively Misusing TLA+
        
       Author : iforgetlogins01
       Score  : 81 points
       Date   : 2023-02-11 09:19 UTC (1 days ago)
        
 (HTM) web link (buttondown.email)
 (TXT) w3m dump (buttondown.email)
        
       | xrayarx wrote:
       | Already posted https://news.ycombinator.com/item?id=34694123
        
         | vichu wrote:
         | This looks like a second-chance pool story as it didn't get
         | much attention last time it was posted.
         | 
         | See dang's comments on the pool here:
         | https://news.ycombinator.com/item?id=26998308
        
           | sbierwagen wrote:
           | I once left a comment on a submission that seemed to go
           | through the second chance pool _twice_ before getting
           | traction, picking up three sets of replies each 24 hours
           | apart.
        
       | zeckalpha wrote:
       | These all seem like good and reasonable uses rather than misuses
       | to me.
        
         | hwayne wrote:
         | "Creative misuse" refers to _intended_ use. TLA+ isn 't "meant"
         | for these things, it just happens to be good for some (and
         | kinda-okay for others). But that's the beauty of tools: it
         | doesn't matter what they were designed to do, you can use them
         | for whatever you need them to do.
         | 
         | It's harder to find creative misuses for programming languages
         | because they're "intended" be general purpose. They're more
         | like a material than a tool.
        
           | user5678 wrote:
           | [dead]
        
         | Smaug123 wrote:
         | Even the general constraint solver? There are tools like Z3
         | which _are designed to_ solve this sort of problem (quickly and
         | exhaustively), and then there are tools like TLA+ which _can_
         | solve this sort of problem (slowly and exhaustively).
        
       ___________________________________________________________________
       (page generated 2023-02-12 23:01 UTC)