disruptek

5 ms·

1. 1.▲
   Nim CPS: compile-time continuations(github.com)

   7 points by disruptek 3y ago|3 comments
2. 2.▲
   by disruptek 3y ago

   Resubmit because I typo'd the link. XD
3. 3.▲
   by disruptek 3y ago

   This'll get you closer: https://github.com/nim-works/cps Sorry, I was in a hurry.
4. 4.▲
   by disruptek 3y ago

   Another in the continuing discussion... CPS as a library using nothing more than Nim's meta-programming.
5. 5.▲
   Nim CPS: compile-time continuations(github.com)

   3 points by disruptek 3y ago|3 comments
6. 6.▲
   by disruptek 6y ago

   You can read about the reasoning behind subgraph ownership here: https://github.com/nim-lang/RFCs/issues/244
7. 7.▲
   by disruptek 6y ago

   Also, we don't scan "live" memory, which matches your intuition -- why would we?
8. 8.▲
   by disruptek 6y ago

   Nim doesn't require that you use a gc; one of its many gc options is `none`, which is, as it sounds, no garbage collector at all.
9. 9.▲
   by disruptek 6y ago

   I want to remove a couple misunderstandings that I see in the comments. Nim is "not done" and I hope it never will be. Watch Guy Steele's "Growing a Language" talk for my rationale. We want a language that can con
10. 10.▲
    by disruptek 6y ago

    Please open an issue if you want to change the semantics; it's trivial to use the hash instead.
11. 11.▲
    by disruptek 6y ago

    Nimph has had lockfiles for months. https://github.com/disruptek/nimph