The second release candidate for Nim v2.0.0 is ready for testing!
See more: https://nim-lang.org/blog/2023/03/31/version-20-rc2.html
Not sure it is related, but something is broken with stable channel and 1.9.3:
Is this expected on macOS M1?
$ file ./bin/nim ./bin/nim: Mach-O 64-bit executable arm64
But after compiling a simple hello.nim file:
$ file ./hello ./hello: Mach-O 64-bit executable x86_64
Can be specific to my system.
Compiled from source.
Nim Compiler Version 1.9.3 [MacOSX: arm64] Compiled at 2023-03-31 Copyright (c) 2006-2023 by Andreas Rumpf
git hash: 2e4ba4ad93c6d9021b6de975cf7ac78e67acba26 active boot switches: -d:release
Is this expected on macOS M1?
I used to have the same problem but I don't remember what I did about it. :-) OSX is weird.
I have the same problem except I cannot even install choosenim because of it. Stable version points to 1.9.3 instead of 1.6...
deck@ubuntu-22-10:~$ curl https://nim-lang.org/choosenim/init.sh -sSf | sh
choosenim-init: Downloading choosenim-0.8.4_linux_amd64
Prompt: Can choosenim record and send anonymised telemetry data? [y/n]
... Anonymous aggregate user analytics allow us to prioritise
... fixes and features based on how, where and when people use Nim.
... For more details see: https://goo.gl/NzUEPf.
Answer: n
Tip: 4 messages have been suppressed, use --verbose to show them.
Error: /__w/choosenim/choosenim/src/choosenim.nim(350) choosenim
... /__w/choosenim/choosenim/src/choosenim.nim(340) performAction
... /__w/choosenim/choosenim/src/choosenim.nim(124) choose
... /__w/choosenim/choosenim/src/choosenim.nim(64) chooseVersion
... /__w/choosenim/choosenim/src/choosenimpkg/utils.nim(29) parseVersion
... Version 1.9.3 is a development version of Nim. This means it hasn't been released so you cannot install it this way. All unreleased versions of Nim have an odd patch number in their version.
Hint: If you want to install the development version then run `choosenim devel`.
deck@ubuntu-22-10:~$ choosenim
bash: choosenim: command not found
The stdlib provides pegs:
When you advertise that, you should at least also mention the great https://github.com/zevv/npeg -- even when you may have your reasons to dislike that one. Advertising one, and not mentioning the great alternatives, confuses newcomers a lot.
Advertising one, and not mentioning the great alternatives, confuses newcomers a lot.
The point was that the stdlib should offer a single thing. And "newcomers" might indeed be confused by choice. Which is a terrible argument in itself as:
Has anyone managed to use sqlite from a 2.0-rc2 build?
The changelog notes:
- Several Standard libraries are moved to nimble packages, use `nimble` to install them:
- `std/db_sqlite` => `db_connector/db_sqlite`
nimble install db_connector
nimble install db_connector
Downloading https://github.com/nim-lang/db_connector using git
Warning: The package has no tagged releases, downloading HEAD instead.
Verifying dependencies for [email protected]
Installing [email protected]
Success: db_connector installed successfully.
Is there something wrong with sqlite3 and this release? I tried to compile with this last version and seemingly it's complain about the module not being found:
Error: cannot open file: sqlite3
nimble install db_connector
import db_connector/sqlite3
What about the idea that came up here at some point that the stdlib could just be a list of curated nimbles, maintained or at least selected by the Nim compiler developers?
https://forum.nim-lang.org/t/7983
With stdlib being nimbles, we can imagine that a next version of the compiler will remove a package from its stdlib, but the package being a nimble, continuing to use it would be a no op (or close to).
What about the idea that came up here at some point that the stdlib could just be a list of curated nimbles, maintained or at least selected by the Nim compiler developers?
That's we're heading but the more we do it, the harder it becomes to port code over to 2.0, so we don't try too hard. ;-)