Mirror of forum.nim-lang.org

13894 :: import vs include for personal/small projects

• kitkat24 (orginal) [2026-05-03T07:45:33+02:00] view original

  Back to working actively on some projects in the language again, curious which y'all prefer. I'm not making like a library, but previously I've always just used import so defaulted to that. Wondering if it's better to include just so I don't need to * everything for myself.

---

• janAkali (orginal) [2026-05-03T10:39:02+02:00] view original

  include is bad for imports:

  1. include A in B
  2. include A in C
  3. include both B and C anywhere
  4. everything explodes

  I'd say just build a habit to put * on most objects and procs.

  There is also all pragma to import private functions and symbols, but that doesn't import private object fields without using std/importutils.privateAccess():

  
  import foo {.all.}
  Run

---