New OSX weirdness - extraneous ld warning

See also fixes #22798; Duplicate libraries linker warning (i.e., '-lm') on macOS

Latest GCC version (14.1) breaks Nim's C backend

I tested . It works with the devel branch.

Latest GCC version (14.1) breaks Nim's C backend

Please open an issue on the gitHub if it doesn't work with the devel branch

Nim 2.2.0 RC1 available

Hi, @Ward thanks for your feedbacks. The issues that you posted are fixed in the following PRs/anwsers: # Issue 1 > Culprit here seems to be #23055 which switched to elementType from base, > probably only worked by chance before. ref

Small libraries you'd like to see ported to Nim?

There is a repo for needed libraries

Nim 2.2.0 RC1 available

issues tracked in

Going from 2.0.6 to 2.0.8 & errors

Well, the changed logic is for refc though. It shouldn't affect orc. You are using [orc](], aren't you?

Going from 2.0.6 to 2.0.8 & errors

Why did you remove `move` in the new implementation? It should be easy to bisect since they are few commits contained from 2.0.6 to 2.0.8

Forum on Firefox is broken

Hopefully the issue around Grammarly with Nim forum will be resolved after the new forum instance is deployed since it has been fixed

template import non compile in nim 2.0.4

It works on the devel as well

Latest GCC version (14.1) breaks Nim's C backend

Yes

Latest GCC version (14.1) breaks Nim's C backend

more fixing for gcc 14 is coming fixes #23665; rework spawn with gcc 14 and fixes other tests => rework ctypes with gcc 14 => gcc 14 CI support will come soon when tests pass =>

Super-weird error with builds on latest Windows runner (Github)

Well, LinenoiseCompletions* {.bycopy, importc: "linenoiseCompletions".} = object len*: csize_t cvec*: cstringArray Run Shouldn't `importc: linenoiseCompletions` be used? It doesn't seem to be a Nim bug to me

Super-weird error with builds on latest Windows runner (Github)

It's related to . Though I would expect a similar fix should be done for `linenoise.nim` or in the compiler.

Latest GCC version (14.1) breaks Nim's C backend

Progress:

Issue: regression on 2.x.x: push warning[HoleEnumConv]:off does not work.

progress:

Issue: regression on 2.x.x: push warning[HoleEnumConv]:off does not work.

The problem is that since , the whole module is parsed at once instead of streaming, which makes `push`, `pop` is quite awkward since we now need N cases to handle push/pop now.

Issue: regression on 2.x.x: push warning[HoleEnumConv]:off does not work.

Thanks for your effort. I will look into this issue

Feature Request: enum: relax or remove order requirements.

See also * values order is not required * automatic numbering is incremental and is reset each time an item with a value is encountered * enum aliases are not supported; for a field definition with numbering, if it's a duplicate, an error will

Feature Request: enum: relax or remove order requirements.

type unordered_enum = enum a = 100 b c = 50 d Run What should the value of `b` and `d`? OR it should be disallowed?

Feature Request: enum: relax or remove order requirements.

What's the value of `c`? Or should it give an error somehow? type unordered_enum = enum a = 2 b = 0 c d = 1 Run

How do I keep track of changing standard-libs?

fwiw you can read for standard library changes

How to remove the N_LIB_PRIVATE from exported c code.

See also => dynlib keeps exported functions alive in emscripten

How to remove the N_LIB_PRIVATE from exported c code.

Neat macros! Let me see whether I can make `__attribute__((used))`/`EMSCRIPTEN_KEEPALIVE` into `nimbase.h`

This forum has an XSS injection vulnerability

progress =>

Do not understand the error when trying to add to seq inside loop

progress：

can't run nim

Yeah, please help us with reporting false postives to AV vendor

=destroy and enum

I think there is no bug here. `eqdestroy___enum95destroy_u88((&(*t__enum95destroy_u12).kind));` doesn't destroy the enum field. It's a hacky way the destroy the old object variant (It uses the address of the start of the object variant) N_LIB_PRIVATE N_NIMCALL(void, eqdestroy___te

Strange Behavior About Nim 2.0 Destructor

progress:

The nim installer for Windows contains malware

fwiw, submits the Nim nightlies binaries to virusTotal everyday

Strange Behavior About Nim 2.0 Destructor

Make sense, the deprecation message will be undone for `refc`

Strange Behavior About Nim 2.0 Destructor

The new destructor should not applied to `refc`, I will disallow it for refc. Did you try the example with `--mm:orc --cpu:i386`?

Enhancing Nim vtable implementation vs subtype checking

> would it be possible to remove the vtables limitation of having to declare > the method in the same module as the type Like the former implementation, the vtable implementation generates dispatchers only in the main module codegen in order to collect all the possible method defintions among m

Enhancing Nim vtable implementation vs subtype checking

Here is the PR for the documentation of vtables for methods =>

No =destroy hook(s) in std/tables?

Here is the progress => fixes #22286; enforce Non-var T destructors by nimPreviewNonVarDestructor

No =destroy hook(s) in std/tables?

I'm looking into this issue. There is another workaround using `var T` destructors: proc `=destroy`(x: var BObj) = echo "Destroying B named ", x.name `=destroy`(x.name) `=destroy`(x.tableField) # Workaround for lack of =destroy in Table Run

related_post_gen benchmark

I created a PR => for it should lent its return value. Though, I surmise it's more of cursor issues, which means `t[i mod 100]` might create an unnecessary temporary.

related_post_gen benchmark

> PRs are welcome. On it

Mastering Nim 2.0

Congratulations on this masterpiece on the Nim language! It has a pretty cover and a comprehensive guide on the threading model in Nim! Nice work!

Exceptions occurring in top level statements of submodule not being reported/handled

杨意不逢，抚凌云而自惜；钟期既遇，奏流水以何惭？ I kept being a half-assed loser and never stuck to something interesting longer than months. Thus, I'm grateful to find the Nim language, which I can pour my heart into, where I found dozens of passionate and great people among whom @araq and @timotheecour have helped m

Template being called twice with Nim 2.0

Thanks for your insights. I will fix it soon. You are so incredible!

Dark Theme Problem in Nim Manual

Known issue =>

Nim version 2.0.0 is here

> I tested it personally on Windows 10 and no such reports. :-/ No problem for me either. I use Win11 and a clever antivirus software.

Nim version 2.0.0 is here

> I tested it personally on Windows 10 and no such reports. :-/ No problem for me either. I use Win11 and a clever antivirus software.

High stack usage when calling `reset` on an object with a destructor

Here is the fix copied from this thread =>

Usability of ARC/ORC in multi threaded code.

Here is the PR adding an experimental mm:atomicArc switch booting: 6.374s (--mm:arc --threads:on) 7.107s (--mm:atomicArc --threads:on)

My Nim Development Weekly Report (4/30)

## Progress ### following-ups [fixes broken CI](https://github.com/nim-lang/Nim/pull/21732) [handle quoted routine symbols and non symbols expressions as before](https://github.com/nim-lang/Nim/pull/21740) [closes #21745](https://github.com/nim-lang/Nim/pull/21746) ### fixes memory leak with

My Nim Development Weekly Report (4/16)

## Progress ### chores [stops building nimsuggest twice and nim_dbg in tests; saves 3 * 5 minutes CI time](https://github.com/nim-lang/Nim/pull/21668) [stdlib tests now check refc too](https://github.com/nim-lang/Nim/pull/21664) [disable i386 tests for now; help wanted](https://github.com/nim

My Nim Development Weekly Report (4/2)

The two features are not implemented. I'm working on them this week.

How could I set up an i386 CI for Nim?

Hey @elcritch I'm running `i386/ubuntu:latest` container on ubuntu-latest. But the problem is the CPU is not 32 bits so that csource building fails.

How could I set up an i386 CI for Nim?

@elcritch Thanks for your suggestions! I will try it again.

State of HTTP Servers in Nim

Here is the PR implementing async streaming => <https://github.com/ringabout/httpx/pull/24> thanks to @termer Feedback is welcome.

Nim v2.0.0 RC2 is out

`nimble install db_connector` import db_connector/sqlite3 Run

How could I set up an i386 CI for Nim?

Probably it can switch to windows i386, which isn't dropped.

How could I set up an i386 CI for Nim?

> ##[error]The ubuntu-18.04 environment is deprecated, consider switching to > ubuntu-20.04 or ubuntu-22.04 (ubuntu-latest). For more details, see > actions/runner-images#6002 With `ubuntu-18.04` disabled, the i386 CI doesn't work anymore => Is there

My Nim Development Weekly Report (4/2)

## Progress ### chores [fixes changelog](https://github.com/nim-lang/Nim/pull/21590) [fixes booting warnings](https://github.com/nim-lang/Nim/pull/21583) ### create type bound operations for calls in the method dispatcher for ORC [fixes #21592; create type bound operations for calls in the met

RFC: compiler support for object construction shorthand (full fields initializer)

Here is my RFC for adding compiler support for object construction shorthand (full fields initializer) => You might leave your concerns there.

My Nim Development Weekly Report (3/26)

Nope, it is used to eliminate the `wasMoved(x); =copy(x, y)` pair.

My Nim Development Weekly Report (3/26)

Yeah, it means Nim 2.0 rc2 is soon.

My Nim Development Weekly Report (3/26)

> One big question though, when can we expect the full release of Nim 2.0 > When some critical regressions and > [showstopper](https://github.com/nim-lang/Nim/issues?q=is%3Aissue+is%3Aopen+label%3AShowstopper) > issues are fixed.

Why Svelte is far superior than React (Karax)

> I remember things like iterators were not properly supported in the > javascript backend, and nclearseam needed to use features like this. Speaking of which, someone might try to port [enable lambda-lifting for the JavaScript target](https://github.com/nim-works/nimskull/pull/586). It seems f

My Nim Development Weekly Report (3/26)

## Progress ### fixes the documentation of typeclasses [closes #21536; fixes manual](https://github.com/nim-lang/Nim/pull/21552). The parser has been changed, now you need to use `type RecordType = (tuple or object)` ro declare types classes starting with tuple or object instead of `type Recor

Do you miss these compact syntaxes?

Fwit, I'm working on [adding compiler support for object construction shorthand](https://github.com/nim-lang/Nim/pull/21559). type Vector = object a: int = 1 b, c: int block: # positional construction var x = Vector(1, 2, 3) echo x

My Nim Development Weekly Report (3/19)

## Progress ### Checks the potential errors with closure calls [fixes #19857; Exception raised in closure may be "skipped" in ORC](https://github.com/nim-lang/Nim/pull/21530). ### Adds a prepass for codeReordering [add a prepass for codeReordering](https://github.com/nim-lang/Nim/pull/21513).

My Nim Development Weekly Report (3/12)

## Progress ### chores [closes #16654; add a test case](https://github.com/nim-lang/Nim/pull/21478). [closes #20704; add a test case](https://github.com/nim-lang/Nim/pull/21480). [closes #6231; add a test case](https://github.com/nim-lang/Nim/pull/21485). [closes #8295; add a test case](https:

Version 1.6.12 released!

There is probably something wrong with `choosenim stable` (probably the server channel hasn't been updated). Try `choosenim 1.6.12`, which works for me.

Version 1.6.12 released!

One of the important fix in this release is that it avoids using old API on Windows, which might improve the false positive situation on Windows =>

My Nim Development Weekly Report (3/5)

Nope, I don't know the deadline for 2.0.

My Nim Development Weekly Report (3/5)

Here are my todos =>

My Nim Development Weekly Report (3/5)

## Progress ### chores [remove nosinks hacks from compiler](https://github.com/nim-lang/Nim/pull/21469). [test DLL generation with ORC](https://github.com/nim-lang/Nim/pull/21445). [fixes sinkinference documentation, which has been disabled](https://github.com/nim-lang/Nim/pull/21470). ### i

Nimble package submission process broken?

Progress All thanks to @Yepoleb

My Nim Progress tracking everyday

To get the latest progress of the Nim development, you might follow To find something easy to contribute to, you might follow The final summary might be published every week

challenges with bool parameter on template

progress

My Nim Development Weekly Report (2/26)

## Progress ### Clean-ups [invalid module names errors have been improved](https://github.com/nim-lang/Nim/pull/21412), it now says that a module name must be a valid Nim identifier. [fixes the linkerexe of riscv64 in config](https://github.com/nim-lang/Nim/pull/21292). [csources_v2 can buil

Nim GitHub statistics

I happened to find some statistics regarding Nim on GitHub, I suppose someone is interested in it. [https://oss-compass.org/analyze?label=https%3A%2F%2Fgithub.com%2Fnim-lang%2FNim&level=repo%27&range=Since%202000](https://oss-compass.org/analyze?label=https%3A%2F%2Fgithub.com%2Fnim-lang%2FNim&lev

My Nim Development Progress Weekly

Sure thing! I'm going to do my best when I'm working on Nim. This week, I'm still following the roadmap and working on which intends to abolish (and deprecate) using passes in the compiler and simplify compilation pipeline, which should make the call

My Nim Development Progress Weekly

Thanks you!

My Nim Development Progress Weekly

First of all, the Nim development follows [The Roadmap 2023](https://github.com/nim-lang/RFCs/issues/503), which specifies what features might be implemented or removed in 2023. As we can see, completing incremental compilation and recursive module dependencies might be the most important tasks

Wanted libraries wishlist?

We need some libraries collection benchmark like to monitor performance regression

`-d:nimPreviewSlimSystem` reduces the execution time of simple nimscript programs to a half

A small speedup trick for simple nimscript programs. On my PC, echo "Hello, World" Run `time nim e test.nims` real0m0.104s user0m0.103s sys 0m0.001s Run `time nim e -d:nimPreviewSlimSystem test.nims` real

Why vtable implementaion is not better than subtype checking implementation?

The vtable might be stored in a global static array in a WIP alternative PR => I'm not sure about the RTTI part.

Why vtable implementaion is not better than subtype checking implementation?

It seems that the vtable implementation works great when there are 50 object types with 5 methods and 100 instances ref 50 object types with 5 methods and 100 instances vtable: `nim c -r -d:release` dummy value: 34803480 time: 0.0054946001 Run the old imp

Why vtable implementaion is not better than subtype checking implementation?

I'm working on <https://github.com/nim-lang/Nim/pull/20897> which replaces the dispatcher using subtype checking with the vtable dispatcher. But in the benchmark <https://gist.github.com/ringabout/0752a22b2c85e737a66314bb61a470e6>, they behave as good as each other. The old

Why I stopped programming in Nim

Like there are feasible solutions for the Nim team. The virus scanners should learn to understand the Nim program. Even the mainstream language Golang hasn't had a good solution. > This is a common occurrence, especially on Windows machines, and is almost > alway

Why I stopped programming in Nim

Like there are feasible solutions for the Nim team. The virus scanners should learn to understand the Nim program. Even the mainstream language Golang hasn't had a good solution. > This is a common occurrence, especially on Windows machines, and is almost > alway

Why I stopped programming in Nim

https://github.com/nim-lang/Nim/pull/19767

Why I stopped programming in Nim

Well, fwiw, the devel compiler or 2.0rc should cause less false positives than 1.6.x

`--os:standalone` gives `Error: system module needs: getCurrentException`

The type mismatch error on devel is probably related to

`--os:standalone` gives `Error: system module needs: getCurrentException`

The devel doesn't crash, which is a good sign. The type mismatch error is probably related to

Multilungual Nimdoc

That's hard to maintain, though. Perhaps you can maintain the Chinese documentation in the separate directory =>

Nim book in Japanese

Not necessarily popular, it is a self-public book like the Amazon one. shows some insights regarding where the visitors are from.

A serious documentation for Nim

I hope to see a better documentation too. I would like to see a gentle introduction for asynchronous and its internal implementation details. It would be appreciated if can be tackled too.

Nim version 2.0 RC1

> It's not an echo "Hello, World!" however. Nim seems to have improved in > binary size since that blog post. Is it due to arc/orc and panics:on? Or > other changes also helped? Since the Nim compiler has defaulted to ORC, the binary has decreased a lot. On my Linux, it drops from 84kb (--mm:re

Nim version 2.0 RC1

Thanks for your valuable suggestions, I have made a [PR](https://github.com/nim-lang/website/pull/352) to solve the concerns. Feedback/Advice is most appreciated!

Nim version 2.0 RC1

Pragmas cannot be placed after the object in v2. mm_gmp_randstate_algdata* {.pure, union.} = object mp_lc*: pointer Run

Windows Defender detected Trojan.AndroidOS/Multiverze in Nim-1.6.10_64.zip

The patch has been a part of v2.

Windows Defender detected Trojan.AndroidOS/Multiverze in Nim-1.6.10_64.zip

fwiw, probably is the cause that 1.6.x has been flagged. We also have been trying to mitigate this issue =>

Nim version 2.0 RC1

It seems to be a choosenim issue, It happened for 1.6.x releases too, please open an issue on the issue tracker of choosenim.

Nim version 2.0 RC1

I don't know whether switching to csources_v2 solves the problem, I have submitted a patch to choosenim =>

Nim version 2.0 RC1

It seems that choosenim only builds Nim with `csourcesUrl = "https://github.com/nim-lang/csources"`.

  1   2   >