That was my first thought! :P Based on the language popularity list, though,
there were closer to 250ish responders using `nim`.
Fun fact! In the recently released [2024 Stack Overflow Developer
Survey](https://survey.stackoverflow.co/2024/technology#top-paying-technologies-programming-scripting-and-markup-languages),
`nim` rose to fourth place in terms of median developer salary. It had the
highest year-to-year growth on
If you would like to process a binary file and assign it to an array without
embedding the binary file itself, you can utilize the `static` block which will
execute at compile time and return just what you need.
It looks great! I was recently searching for a neat example written in Nim.
Thanks for sharing!
As @thindil suggested, you may want to use _std/unittest_. It generally works
great for small projects where you may not need any of Testament's cool
features like multiple targets or report generation.
[Here is an
example](https://github.com/amkrajewski/nimCSO/blob/main/
You can give [Windows Subsystem for Linux
(WSL)](https://learn.microsoft.com/en-us/windows/wsl/install) a try if you are
not developing your tool specifically for Windows. You can connect to WSL,
e.g., with VSCode, and get a very smooth experience. In the case of several Nim
codes I tried, it i
How did you install Nim? Homebrew, choosenim, or built it yourself?
At some point I’ve had some similar flavor (x86_64 vs ARM64) of problems on my
Mac M2 when I installed Nim with choosenim. They all went away when I cloned
repo and compiled Nim on my own.
It seems that having a simple „Verified to work with Nim: 1.4.8, 1.6.16, and
2.0.0” in README and updating it every once in a while may be very helpful at a
near-zero cost.
In my research group specializing in computational materials science and
thermodynamics, I've been advocating for using Nim roughly once every two weeks
with some success, as we have already reimplemented two Python packages we use
internally.
Some of my colleagues who almost exclusively use Py
That's a good catch, though the off-centering is by design. I offset both text
fields by 5% of the height because (to my taste) it looked much better for the
"v1.2.34" version tag (by far the most common pattern in Nimble) because of the
little "v" being inherently offset towards the bottom. It
Adjusted and should propagate soon 🙂
Versions longer than 9 total symbols are now resized and centered to neatly
fill the available space.
It should work pretty well, even with very long ones.
or
Thanks for pointing that out! I tested for up to 3 "." and 7 digits/characters,
but DateVers can reach 9. I will make some adjustments and let you know.
When working with PyPI etc., I like to use version badges, especially for
indexing tools, but I didn't see any suitable option for that with Nimble, [so
I created mine](https://github.com/amkrajewski/nimble-badge). It has been
stable for about a week now, updating every 12
Not an answer really, but I hope an extra data point helps. I'm using Nim 2.0.0
in VS Code (1.82.2) with Nim extension (the one by nimsaem) on MacOS (Darwin
22.5) and the "Go to Definition" works as intended.
14 matches
Mail list logo
