Massive Funding Coming To Nim

Sorry guys, I have to stop using Nim and I will become an Excel guru. That's the common tech everyone uses at the companies with tons of money. Even government are using it to great success to stop COVID.

Looking for collaborators!

vm ~ virtual machines covers: * virtual machines * emulation including old CPU/console emulation * interpreters * JIT * assembly/assembler * languages built on top of Nim but otherwise `virtual-machines` or `interpreters` might be the best.

Massive Funding Coming To Nim

Here's a tip for those using Excel's hot new Wide-Column Store mode: reached the 16k limit? Simply split your data into multiple files.

Looking for collaborators!

Well, count me in! I guess there are many people far more knowledgeable than me in this field, but given that I've been playing with interpreters/compilers/grammars/etc for the past 15 years, I hope there is something that I can contribute. :) And, yes, in that aspect, Nim seems like a perfect

Massive Funding Coming To Nim

This reminds me of the fake Stroustrop interview :

Massive Funding Coming To Nim

Oh no that harmful.cat-v troll page... I still don't know what's so great about the vi/Unix/C/awk setup, they are so awkward most industries moved away from them...

Massive Funding Coming To Nim

Real Programmer™ use butterflies anyway (from [xkcd](https://xkcd.com/378/) )

Looking for collaborators!

Hopefully I'll be able to find collaborators for my project there :')

Help with SPI Api on ESP32

Since code size might become an issue, you should use `openArray` instead of a generic `array`: proc newSpiTrans*(spi: spi_device_handle_t; data: openArray[uint8] ... Run I don't know if you should avoid the `ref object` wrapping, usually

-d:danger versus -d:release --checks:off

> Well people read the source code successfully. Can't get more definite than > that. :-) Well, as you can see from this thread several people read the same code and arrived at different conclusions :-) The definite answer is how compiler reads the code :-)

-d:danger versus -d:release --checks:off

Good god if we can't know how the compiler reads code we should all go home

Reference to tuple type

Hi, I try to use a `ref` to a tuple type, but I'm getting an error which I don't understand: `Error: () must have a tuple type`. An example code: type MyTuple = tuple a: string b: int proc newMyTuple(a: string, b: int): ref MyTuple = new(result) resu

Reference to tuple type

It seems like you can't make a `ref tuple` constant (even if you could, it's kinda hard to understand what exactly it will give), so as a workaround you can replace `const` with `let`.

Help with SPI Api on ESP32

> Since code size might become an issue, you should use openArray instead of a > generic array: So the compiler generate a separate function for each `array[N, uint8]`? Ah yah that'd be unfortunate for code size. Thanks! > I don't know if you should avoid the ref object wrapping, usually C code

Reference to tuple type

If you don't need to use `const` here, then don't use it and use `let`, this is a compile time VM specific bug and the compile time VM doesn't handle stuff with pointers/references well.

Reference to tuple type

Thx! I'll use `let`.

Massive Funding Coming To Nim

I've got two commercial software in the pipeline proudly being written in pure Nim. Was never going to mention it, but 3% of profits will be going to the developers. I agree man, this language just needs more marketing because it definitely stands strong on it's own merits. I was even thinking

Massive Funding Coming To Nim

Please add your company to if it's not secret info :)

Reference to tuple type

> Since it is a bug,... It is not a bug. You cannot use reference types in expressions executed at compile time. From Nim's official documentation: Restrictions on Compile-Time Execution Nim code that will be executed at compile time cannot use the following language feat

Reference to tuple type

The example screams "use an object type instead" to me.