1. 7
  1.  

  2. 3

    Oh man this is such a bad idea. A great hack, but a baaaaad idea.

    1. 1

      looks neat for simple stuff like library wrappers, but I’d be extremely hesitant to use it for anything more complicated.

      1. 1

        looks neat for simple stuff like library wrappers, but I’d be extremely hesitant to use it for anything more complicated.

      2. 3

        The name of the library mentioned in that post unfortunately clashes with another NIF-related project.

        This is a pretty cool use of parse transforms! Unfortunately, from what I’ve seen, NIFs aren’t usually as small as in the example in the post, so it usually makes sense to have them in their own files. I also view the complications involved with writing a NIF as a test to see if I really want to use a NIF over a safer alternative. If writing NIFs were really simple, I might be tempted to use them more often than I should.