Mirror of forum.nim-lang.org

5721 :: Proc and Iterators with Result Variable

• solo989 (orginal) [2019-12-22T09:33:16+01:00] view original

  I noticed when I took getImpl of a typed closure or proc there was an extra node dedicated to the result variable.

  Not noticing it led to some truly confusing error messages when I was trying to take an existing proc and make a new proc derived from it.

  I would suggest adding an extra slot into untyped procDefs that will be newEmptyNode() when the proc hasn't been typed yet.

  Or at the very least this feature should be better documented in macros.nim.

---

• solo989 (orginal) [2019-12-22T10:31:52+01:00] view original

  I also noticed that the return statement in typed procs turns

  return 5
  Run

  into

  return result = 5
  Run

  which is invalid code if you turn the result variable into an ident.

  This should probably be documented better as well.

---