Weird import issue

I use custom JSON generation code, it's controlled by exporting `to_json_hook` proc. The issue is that it's not imported properly, behaving in a weird way. The code below should print `[{"text":"Some text"}]` but instead it prints `[{"isUnquoted":false,"kind":5,"fields":{"text":{"isUnquoted":fa

Nim online playground using Monaco and Wandbox api

Wow! I wanted to suggest to give access to command line. It seems that with new tabs + config.nims it is already enough access to make "defines" and other configurations. :-) nice job! ps: looks like that zoom bug is no more.

Nim online playground using Monaco and Wandbox api

try this new version: you can now create tabs! currently I can't test windows display setting so that bug may still exists... :(

Memory leak with ARC and malloc when using references and casts

The reason that it doesn't leak without `-d:useMalloc` is because nim holds the memory in case it needs to be reallocated to the leak may not be as easily detectable

Memory leak with ARC and malloc when using references and casts

There is also the .cursor pragma, maybe you can avoid the table altogether somehow?

Memory leak with ARC and malloc when using references and casts

For completeness I'll mention how I solved the issue (at least how I _believe_ I solved the issue). For that I will shortly describe what I actually wanted to achieve. I wanted to create a small entity component manager. For that I need a type `TypeVector`, that can do something like this:

Nim 2.0 -- thoughts

Here's an [RFC](https://github.com/nim-lang/RFCs/issues/361) and here's a [PR](https://github.com/nim-lang/Nim/pull/10781) \- the latter a victim of the fine stable bot . > Can we change so that we don't need compiler flags to turn on threading by > Nim version 2.0?, at least when ARC/ORC are u

Nim is just so great, works first try

Over time we will realize that Nim-Language is solid and allows to create logical and readable code, simple.

Memory leak with ARC and malloc when using references and casts

My guess: In this expandarc output, `:tmpD_1` is a temporary variable introduced to hold the `new seq[Component]` call. It it then in effect cast _and copied into r, that increments the underlying reference counter, both ``r`` and ``:tmpD_1`` shares a reference to the same buffer but with differ

Mac GUI

So excited about this. Is there any reason it couldn't be extended to iOS? Happy to contribute eventually (after substantial learning...!)

complaining about nim popularity.

> Bad documentation. Documentation should be as of python which supports > offline too and should be included in installation also no direct access to > download nim documentation offline. if nim has to be as popular as python > then plz include example in documentation for every single procedur