Mirror of forum.nim-lang.org

5648 :: What are the compiler defaults? etc...

• marks (orginal) [2019-12-07T09:45:47+01:00] view original

  In https://nim-lang.org/docs/nimc.html it shows all the compiler options, but it doesn't seem to show the defaults. How can I find out what they are?

  Is there a pragma that would force names to be fixed? For example, if I do import mod and get afunc in my namespace, what I also get in effect is aFUNC, aFunc, etc., whereas I'd prefer just one. (I realise this is unlikely to be available or even possible.)

  Is there any runtime cost in doing import mod compared with from mod import foo, bar? Is import mod recommended rather than from mod import ...?

  On Windows I used the prebuilt .zip but on Linux I built it myself. I think it might be worth adding to the instructions to run ./koch nimble since ./koch tools doesn't seem to build nimble.

  Incidentally I tried nim a couple of years ago and gave up mainly because I couldn't get it to reliably install on Windows. Now I've installed on Linux and Windows and finish.exe works fine. It gave an error when it came to fetch mingw but instead of giving up it offered to get it from nim's site and when I said yes it "just worked". What I'm looking for is a language as convenient and fast to develop with as Python but with static typing, easy deployment (single executable), and C-speed runtime. Which is why I'm trying nim again.

---

• Araq (orginal) [2019-12-07T13:10:20+01:00] view original

  • Not easy to answer, roughly speaking all runtime checks are active by default and you get a debug build.
  • Use the new --styleCheck:error compiler option.
  • Imports have no runtime cost and Nim optimizes procs out that you don't use.
  • Here is the section of koch.nim

  of "tools":
          buildTools(op.cmdLineRest)
          buildNimble(latest, op.cmdLineRest)
  Run

  as you can see, "koch tools" does bulid Nimble.

  What I'm looking for is a language as convenient and fast to develop with as Python but with static typing, easy deployment (single executable), and C-speed runtime. Which is why I'm trying nim again.

  Sounds like a good description of Nim for me.

---