Mirror of forum.nim-lang.org

240 :: Error: redefinition of 'putsomenamehere'

• caio (orginal) [2013-09-16T06:54:58+02:00] view original

  The following code:

  from module1/views import App1View
  from module2/views import App2View
  Run

  Causes Error: redefinition of 'views'

  Which is clear but seems odd because I'm specifying what I want to import (I don't want anything else). And yes, I know that this is a feature.

  But I'm here to ask a few things:

  • Is there anything that can be done to prevent this behavior? A pragma?
  • Are there ideas to make full qualification be "module1.views" instead of "views" in the future?

  I think this could cause a lot of conflicts, specially while designing modular applications.

---

• dom96 (orginal) [2013-09-16T19:46:44+02:00] view original

  indeed, this is a known bug.

  Last time I spoke with Araq he said he would fix it. This is an even bigger problem in the context of babel packages because it may be very common that you want to import a 'utils' module from two different packages.

  As far as I know, the only way that you can get around this is to prefix your module with something unique.

  Are there ideas to make full qualification be "module1.views" instead of "views" in the future?

  I think that will come once this is fixed, since resolving conflicts would be impossible otherwise.

---

• caio (orginal) [2013-09-17T03:37:28+02:00] view original

  Very nice. This would solve the problem. :)

  What's the point in having full qualification even using the "from ... import" statement?

---

• Araq (orginal) [2013-09-17T18:24:50+02:00] view original

  It's not a bug. However since everybody loves "universe.earth.programming.languages.nimrod.package.utils" you'll get it.

  But beware: Wie man sich bettet, so ruht man.

  ("You've made your bed and you'll have to lie in it.")

---

• Jehan (orginal) [2013-09-18T02:03:35+02:00] view original

  I think a cleaner solution would be to allow for renaming of imported modules, e.g.:

  
  import module1/view as view1
  import module2/view as view2
  Run

  This would allow for disambiguation without ultra.long.symbol.prefixes.

---

• caio (orginal) [2013-09-18T14:18:52+02:00] view original

  I like the way Jehan suggested, for the "import ..." statement.

  For the "from ... import ..." statement I think that the access through full qualification can cause misunderstandings. When I could just see at headers and conclude what exactly is being used.

  from module1/view import only view1, foo
  from module2/view import only view2, bar
  Run

  from module1/view import only view as view1, foo
  from module2/view import only view as view2, bar
  Run

---

• Araq (orginal) [2013-09-25T21:22:13+02:00] view original

  I've implemented:

  
  import path1/view as view1
  import path2/view as view2
  Run

  Also you can now use '.' instead of '/':

  
  import path1.view as view1
  import path2.view as view2
  from x.y as z import nil
  Run

  Only module names can be aliased with 'as'.

---