Nim : Style insensitivity , snake_case , camelCase

I see, I didn't read that part. From my very limited experience I get the feeling that I would like at least the internal consts to be consistent, so it's easier to remember. I think I understand the idea to be flexible about uppercase here, in case some people want to use ALLCAPS consts.

Nim : Style insensitivity , snake_case , camelCase

That "NEP" was accepted long ago and it's the official style guide. And it says: > All other identifiers should be in camelCase with the exception of constants > which **may** use PascalCase but are not required to. So the consts in system.nim adhere to the style guide. What do you think should

Nim : Style insensitivity , snake_case , camelCase

I'm a newcomer to Nim and also more or less a refugee from Python. After initially balking at the case-insensitivity stuff, I've found that it is not really a problem, except for one small annoyance. Because of case-sensitivity of the first letter, I naturally started leaning towards using Pasca

How to implement VEH with nim?

Is it possible to implement VEH just by nim without converging C?

How to implement VEH with nim?

Sure, what you can do in C, you can do in Nim.

Would the Nim version number be helpful in deprecation documentation?

We usually add the version information, for example: "Deprecated since v1.4; it was more confusing than useful, use `[]=`". Run Unfortunately not in your case though...

A rant about Nim bugs

I looked at those bugs originally mentioned, and this one in particular about the high(int32) loop construct: echo "starting" #for i in 0 .. high

Would the Nim version number be helpful in deprecation documentation?

I was just using sequtils delete. I saw one form was deprecated: So I used the newer one, which was fine with the latest nim-git. But in Nim 1.4.8 it fails, the older version is required. I can write some Nim versi

Bug with peekableOutputStream?

Calling `peekLine` to `peekableOutputStream()` is not currently supported. `peekline` proc in `lib/pure/streams.nim` uses `getPosition` and `setPosition` proc but pipe cannot get or set read/write position.

A rant about Nim bugs

Let me start by saying again that I understand and respect the choices you made. But let me also say that I don’t agree with some of your statements. In particular, the (very commendable) fact that you report and fix every issue you find in nim 1.2 in later versions of nim is not (IMHO) and adva

Bug with peekableOutputStream?

Hello there, It was my understanding that `peekableOutputStream` would allow to use `peekLine` calls on a `Stream`. However, the following code spits out a runtime error: import osproc, streams let process = startProcess( "echo", args = ["HELLO"],

A rant about Nim bugs

> However I don’t understand how most of them help the overall evolution of nim It does, by treading a path for anyone else that is looking for a pragmatic way to solve problems without dealing with the general instability - it also helps inform Nim on the problems that arise when someone starts

A rant about Nim bugs

> @arne, can you explain what do you mean when you say that you “test across > nim versions”? You also said that you locked the NUL version you use to 1.2, > so are you testing across different point releases of 1.2 or are you also > testing 1.4 and/or 1.6? I'm not working at status but I'm gue

Advent of Nim 2021

Welp managed to use `foldl` for all except the last day... Still, all in good fun!

A rant about Nim bugs

@arne, can you explain what do you mean when you say that you “test across nim versions”? You also said that you locked the NUL version you use to 1.2, so are you testing across different point releases of 1.2 or are you also testing 1.4 and/or 1.6? I find most of the actions that you describe

can we write nim instead of c++?

You are in the Nim forum, you know (inside?) that you definitely want Nim instead of C++. If you have looked into C++ for your backend, what are your findings, which libraries would you depend on? the Nim eco system is quite small, see if there are matching libraries in Nim see:

A rant about Nim bugs

Being heavy users of nim in one of the larger nim projects out there, we've certainly been taking part in this journey to make Nim more "production-friendly". A lot of our work revolves around building a community whose values include stability and quality overall, and Nim has made huge strides

any way to extra version info from .nimble file?

Even though it doesn't cover all use cases, I think the solution mentioned in @zio_tom78's last comment is common/important enough that it deserves explicit mention in the docs somewhere... maybe [here](https://nim-lang.org/docs/nimscript.html) or [here](https://nim-lang.org/docs/nims.html)? Al