1. 38
  1.  

  2. 6

    This sounds similar to how Pony does things

    1. 3

      Yup, though Pony takes it a bit further by introducing many different reference types/capabilities.

    2. 3

      Thanks for sharing this! I really like the idea of reference counting with panic + single ownership, but I didn’t see that in the wild yet

      1. 2

        A nice writeup, Inko is one of those things I’m keeping an eye on.

        1. 1

          The idea of a mistake in borrowing semantics leading to a runtime panic gives me the heebie-jeebies. But it’s definitely an interesting and novel take on the problem, will be interesting to see how further work on this goes.

          1. 3

            It’s like the segfault you get in C, but deterministic and maybe a backtrace, I guess.

            1. 3

              The segfault you get if you’re lucky.