--gc:orc when is it usable (huge compile times)

You can do git bisect on tags or branches too, so you could do git bisect start git bisect good v1.4.8 git bisect bad devel Run Just don't forget to `git pull` beforehand.

--gc:orc when is it usable (huge compile times)

I can confirm that my application compiles fine with Nim-1.4.8 here, as well. So, what is the first commit after the release of Nim-1.4.8 - I could do `nim bisect` then. Thanks, Helmut

Accessing object properties where objects are in a sequence

Unfortunately switching to -d:release crashes the app without any error messages or gives me this error message then crashes: Error: SIGSEGV: Illegal storage access: (Attempt to read from nil?) Run The same code works without crashing or any error messages when not usi

config files: Nimscript and Nim compiler documentation inconsistency

IIRC like so: switch("arm.linux.gcc.exe", "valueHere") Run

Thoughts on pure Nim api for SPI & I2C device access?

Shouldn't be a problem to create a `const` object that contains information about the registers or file-like objects (for Linux) relevant to the specific bus. Then `init` can do some some work on those registers/file-like objects. Some devices have configurable sercoms (

Nim for Beginners #26 Reference Objects

_“Another noteworthy characteristic of this manual is that it doesn’t always tell the truth. When certain concepts of TeX are introduced informally, general rules will be stated; afterwards you will find that the rules aren’t strictly true…. The author feels that this technique of deliberate lyi

Nim for Beginners #26 Reference Objects

> I know from my experience learning on my own via YT videos, books, in school > and from classmates that you REALLY should not go into technicalities any > more than absolutely necessary, because they will get confused, won't know > what you are talking about and lose interest. That was my reas

Nim 1.6.0 RC1

Except from the Nimble requirement, this is now up-to-date (to the best of my knowledge anyway):

How to enable incremental compilation?

It's unfortunately blocked until is in a mergable state. Feel free to help but the refactoring is both essential and too risky for 1.6, so 1.8 or later will have incremental compilations.

Nim 1.6.0 RC1

I feel there is a need for better sharing. This is our milestone plan, we want to implement the following features We think the features should be prioritised because... if anyone has a concrete rejection with a good explanation please tell us. every week or two weeks, tell us the progress. nee

Thoughts on pure Nim api for SPI & I2C device access?

I like your usage of send/recv vs read/write. Seems to match the nature of the hardware protocols better. Intriguing usage of static. I could've used that the other day! Though I'm not certain how well static would work for some platforms. On Linux you need to open and configure the i2c/spi dev

How to enable incremental compilation?

Hello, How do I enable incremental compilation in the compiler? IIRC, it happens in the koch build, but now that there is a new (work-in-progress) implementation I don't know if it still works (either the previous or the current version). I have a large project, which I hope will benefit from t

Thoughts on pure Nim api for SPI & I2C device access?

When working on Badger I tried to design the interface to be as generic and applicable as possible: . The idea is that every platform will have a static I2C object that details specifics about the platform and exposes one or more such `I2CBus