overload operator `+=` for private member

add proc m*(o: var Obj): var int = o.m Run

proc/func/method: syntax

for 2: this would then be inconsistent with variable declaration, which I think was the reason the syntax is like this in the first place for 3: I don't think this is important as there are still other syntax elements which make it significantly different from Python

Nim boilerplate

your concepts are wrong, saying that type CircleShape = concept a a.r buildCircleProps(a) Run means that for anything to match CircleShape, it must already have a buildCircleProps defined for it. if you do not want that, you remove the build() lines an

Table lookup problem

bug exists on 1.6.14, but not on devel it seems

macro compile-time comparison with define-pragmas

For getting the source file name

Mr. Rumpf, why didn't you went along with the Python standard library?

because nim is not specifically aimed to be similar to python in every sense

Get time at compile-time

There is which is the time when the compile is initiated.

Ways to tweak the output of the JavaScript backend

For specifically removing the numbers? No, not that I know of

Wierd behaviour with table

you have to also `import tables` inside module b

AI’s opinions on Nim

nlvm confirmed for upstreaming in the future

Compiler ignores my `if` a throws an error

The type of I and the return type MUST be known on compile time. Nonetheless, this can be fixed by replacing the if with a when (converting the run time check into a compile time check)

Hopefully simple Nim syntax question

in the first lastStoneWeight, `proc lastStoneWeight(stones: var Stones): int`, it requires a var. `var stones = weights.mapIt(Stone(weight: it)).toHeapQueue` makes a var or a variable to a mutable value, okay, and you pass it. `result = lastStoneWeight(stones)` but here, `lastStoneWeight(weigh

Simple linked list questions: Correct proc signature for first()

`proc first[T](list: var SomeLinkedList[T]): SomeLinkedNode[T]` also `result = list.head[]` must be `result = list.head`, you musnt dereference it otherwise you get the `Obj` version which isnt the return type you list

best practice or guidelines on using log in a library?

with regards to “convince”, you make a good library and advertise it then people will use it. what’s wrong with manually editing the libraries you need info from? You don’t really have the choice to otherwise I believe

closure and for loop problem

needs closure scope capture

Thoughts on error vs fatal log levels?

If your program has no choice at all but to exit, use fatal If your program can recover in some way from the error, use error

What approach can I use to fix a number of parameters in some functions?

excerpt: using c: Context n: Node counter: int proc foo(c, n) = ... proc bar(c, n, counter) = ... proc baz(c, n) = ... proc mixedMode(c, n; x, y: int) =

Error: identifier expected, but got: paramStr(1)

declared is a compile time construct, paramstr is a runtime construct. declared cannot take information from paramstr

More nim newbie woes, this time echo fmt Possible AOC2021 spoiler

Try updating Nim or using a stable version, it seems like you are using a nightly which may be broken

proc doSomething(msg="", opt=-1)

No, because that would require the lexer to know beforehand about procedures and other context. Also no because that would break older code that might have depended on this, and no, scanning public repositories for use of such does not act as proof, nor does “it makes no sense”

Indentation in Nim

what exactly is your point? you just rebutted both of your options

include std/prelude vs import std/prelude (and other small prelude oddities)

There is no need to special case the module, you can re export modules imported (acting like an include without being an include) but for some reason prelude doesn’t do this

The fate of Nim Editors

usually the completion plugins themselves implement "statistical completion", usually called buffer complete or something like that for vim (at least it was called that in nvim-compe).

Direct I2C device access with pure Nim

You probably need to flush the file before closing though I’m not sure if it is already automatically done if closing

Does Nim have anything equivalent to Ruby's puts, or Python's print, or Perl's say?

Does echo not already put a new line after the string you echo?

A look at Dart's null safety syntax

i believe the "none" and "some" functions are needed because of the type system nim has

Template or macro for heterogeneous tuple expressions?

You can probably use an implicit generic (`tuple` with no generic parameters) and use

documentation for the `do` keyword?

it is found in the experimental manual albeit it being used often tldr do w/o parens is just a code block, do with parens is an anon. procedure let a = do: # or block: 0 let b = do () -> int: # or proc (): int = 0 Run

How to get the compile time as a const string?

There is already a constant with the compile time

Why is there no compile error when accessing uninitialize variable

"uninitialised" variables are actually default(/zero)-initialised if nothing is set, so it's equivalent to `var theValue = default(int)` and so

`sleep_async` behaves as if it's blocking, strange

im getting the expected output with the same code and parameters, more data would be needed to determine what is wrong

Splat operator in Nim?

Your seq is impossible, sequences are single type only

Sorting array by object key

did you export `d`? `d*: OrderedTable[...]` (note the asterisk)

echo doesn't work correctly

echo adds a new line, use stdout.write() instead

Why does JSON serializing a table not work properly?

ah good point, using numbers is valid for js objects but not json i assume.

Why does JSON serializing a table not work properly?

looking at , there is no toJsonHook for Table[int, string]; this means you have to provide one, unfortunately.

Alternative to float

float64 is the equivalent to double in nim if you truly want to avoid float errors, perhaps consider using a decimal library, there should be a few of those on github

How to know where a proc is defined - or: Newbie tries to get used to unqualified imports

hello, you cannot use UFCS with qualified imports which is why it is not recommended echo nimdata.collect(nimdata.fromRange(nimdata.DF, 0, 10)) Run

"||" operator ? : Is there a corresponding operator for iterables ?

Where do you see this || operator? I have never seen such an operator in Nim...