nimcuda

I can not really help you sadly, since I own a too recent GPU for nimcuda (which only supports up to cuda 8.x don't remember the exact number). (I don't have vector_types.h header). I don't know how to install cuda 8.x without messing with the whole system. Can you maybe precise how you build w

How to properly typecheck a variable number of array args?

proc staticLengthCheck[A, B: static[int]](a: array[A, int], b: array[B, int]): array[4, int] = static: assert A + B == 4 discard # do stuff here discard staticLengthCheck([1], [1, 2, 3]) # ok discard staticLengthCheck([1, 2], [1, 2, 3]) # compile time

Is Nim good for creating video games?

Please stop making cool video games, because it almost leaves me with no time to study. Lol. I really can't concentrate on my studies because I spend all my free time playing cs go. I wanted to take a break from video games, and was determined. I found a site where you can sell their skins:

Is Nim good for creating video games?

Please stop making cool video games, because it almost leaves me with no time to study. Lol. I really can't concentrate on my studies because I spend all my free time playing cs go.

Nim 1.6.8 released!

Is the plan to release a 1.6.10 soon to fix this problem?

How to properly typecheck a variable number of array args?

I have a statically sized array, and I want to create a constructor proc for it that accepts a list of other (statically sized) arrays. The sum of the sizes of the input arrays must then equal the size of the array being constructed. I know that the information necessary to check this should be

Nim 1.6.8 released!

I tried disabling this behavior with --styleCheck:off but it did not work. Is that normal? This is really annoying because it applies to code that is not "yours" (i.e. to code that you import from external packages).

Nim 1.6.8 released!

Yes, see the issue closed by the PR, .

EpochTime substractions gives out small negative float

I took a look at the monotimes module before asking, still gonna try to use it.

EpochTime substractions gives out small negative float

See Read about how "monotonic time" in computers work.

EpochTime substractions gives out small negative float

Hey, Im trying to add an ETA to one of my programs, what I do is multiply the time taken between to loop iterations and multiply it by whatever remaining iterations. But for some reasons subtracting two epochTime result (float 64 I assume) always gives out a really small negative float, somethi

Nim cross-compiled in OpenEmbedded

I have cross-compiled Nim version 1.6.8 in OpenEmbedded and also greatly refined the build recipe, having learnt a bit more since being a raw beginner a couple of weeks ago. I have posted the OE build recipes here:

Nim 1.6.8 released!

This is a mistake, this is the `--styleCheck` option but it is not supposed to be enabled by default. The bugfix for this was not backported by accident, see

Nim 1.6.8 released!

Docker images for 1.6.8: [https://hub.docker.com/repository/docker/nimlang/nim/tags?page=1&ordering=last_updated](https://hub.docker.com/repository/docker/nimlang/nim/tags?page=1&ordering=last_updated)

Nim 1.6.8 released!

I just upgraded the FreeBSD port, and I'm surprised that I now get pages of hints, such as the following: Hint: 'object_parent' should be: 'objectParent' [Name] This is plainly wrong, as I intended this name to be precisely as it is and strikes me as being somewhat opinionated. Is there some re

Where to start with creating direct Qt bindings?

I have some hello world example, and I also have written already some complex programs with it. I'm planning to release it, but it's now still all very my-system-centric, and I want to improve on that (and, as said before, improve the parsing). IIRC I also had some problem with conversion of fl

Where to start with creating direct Qt bindings?

Excellent 👍👍👍 Do you have a `hello world` that actually works? Will you release the library?

Overriding default C/C++ options + error with 1.6.8 / C++ / macOS

You can find the entire project here: I build with `./build.nims install` The resulting compilation command+flags for the above test are: nim c --skipUserCfg:on --colors:off -d:danger --panics:off --mm:orc -d:useMalloc --checks:off -d:ssl --c

Overriding default C/C++ options + error with 1.6.8 / C++ / macOS

What's your compilation options?

Where to start with creating direct Qt bindings?

I have written something that parses the Qt headers and then emits nim files, together with some macros that allow inheriting from a QObject. It is using treesitter for parsing, but there are too many exceptions for it to work properly, so only a small portion of headers have been converted. So

Overriding default C/C++ options + error with 1.6.8 / C++ / macOS

I think I will agree... I believe the culprit is this PR you mentioned: The problem is... the project is written purely in Nim + C (and Arturo), with literally _one_ `.cc` file, which - as I said previously - I struggled to get it to compile (without

IndexError: list index out of range

Thanks for the good information [url=

Overriding default C/C++ options + error with 1.6.8 / C++ / macOS

> It didn't get backported to 1.6.8 Bummer.