Mirror of forum.nim-lang.org

5548 :: How to avoid recursive module dependency ?

• kcvinu (orginal) [2019-11-17T17:31:21+01:00] view original

  Hi all, I have a recursive module dependency. How to solve this ? Say, i have two modules like this.

  #module_A.nim
  type
      a_Type* = ref object
          aVar* : b_Type
  Run

  And in another file,

  #module_B.nim
  type
      b_Type* = ref object
          bVar* : a_Type
  Run

  How can i avoide recursive module dependency ?

---

• lqdev (orginal) [2019-11-17T17:36:47+01:00] view original

  When you have types that depend on each other, you must place them under one type section—there's no way of avoiding that.

---

• Stefan_Salewski (orginal) [2019-11-17T17:42:20+01:00] view original

  See also

  https://forum.nim-lang.org/t/4745

---

• juancarlospaco (orginal) [2019-11-17T18:50:02+01:00] view original

  Put types on a dedicated file, include it.

---

• kcvinu (orginal) [2019-11-18T05:48:18+01:00] view original

  Thanks for the reply

---

• kcvinu (orginal) [2019-11-18T05:49:03+01:00] view original

  @Stefan_Salewski, Thanks.

  @juancarlospaco Let me try.

---

• leorize (orginal) [2019-11-18T13:59:00+01:00] view original

  This can be useful as well: https://nim-lang.org/docs/manual_experimental.html#package-level-objects

---

• dom96 (orginal) [2019-11-18T17:41:30+01:00] view original

  I would strongly recommend avoiding include as much as possible, and in particular in this case.

  What works usually is to create a module for your types, or to think about how you structure your program, usually you will see that you aren't organising your code in the best way.

---

• mratsim (orginal) [2019-11-18T18:28:45+01:00] view original

  Second that, include will effectively duplicate your type declarations and will probably cause your code to get ambiguous symbol warnings.

---

• treeform (orginal) [2019-11-18T20:01:49+01:00] view original

  I second dom96, recursive module dependency is a sign of bad code organization.

  Avoid it.

---