Nim 1.6.0 RC3

`choosenim "#version-1-6"` so it's not commented out ;) C:\Users\user>choosenim update self Updating choosenim Info: Already up to date at version 0.8.2 C:\Users\user>choosenim "#version-1-6" Info: C:\Users\user\.choosenim\downloads\dlls.zip already

Nim 1.6.0 RC3

It is time for our **third and final** release candidate for 1.6.0! You can download it from our nightly builds: The reported Choosenim bugs should be fixed now, so if you're usin

Nanim: Inspired by 3b1b's manim, I created a GPU-accelerated framework for smooth animations in Nim!

# ❤️❤️❤️

Show Nim: Boxy, 2D GPU rendering with a tiling atlas and Pixie

Boxy is not replacing Fidget but instead is an important piece of our Fidget2 work. We split it into its own repo so others could use it or reference it for their own stuff.

Nanim: Inspired by 3b1b's manim, I created a GPU-accelerated framework for smooth animations in Nim!

This should go on "This month with Nim"

Nanim: Inspired by 3b1b's manim, I created a GPU-accelerated framework for smooth animations in Nim!

Hello everyone! For the last year I've had a hobby of creating smooth animations / motion graphics and uploading them to my instagram. I did it daily for a very long period and while doing it I developed a library with which I could create these animations, and I just made it public here:

Nanim: Inspired by 3b1b's manim, I created a GPU-accelerated framework for smooth animations in Nim!

Amazing! Awesome job :)

Child process shows exit code -1 when peeked, though it has definitely ended.

This appears to be the information I was missing. Thinking back, I definitely made a change that increased the lines written by the child processes, and this also explains the behavior of the peeked code changing when reading the output. Thank you.

Show Nim: Boxy, 2D GPU rendering with a tiling atlas and Pixie

Is Boxy going to replace Fidget? or Be the new Fidget2 ?

Strange compilation error with Nim 1.4.6 on Mac

This compiles and runs for me on macOS 10.15.7

Nim : Style insensitivity , snake_case , camelCase

If you learn other statically typed programming language like C++/D/Rust etc, you would find Nim is actually closer to them rather than Python. Nim code is just looks like Python rather than C++/D/Rust because Nim don't use `{}` to make a block and doesn't require `;` in an end of line. Some pe

Child process shows exit code -1 when peeked, though it has definitely ended.

Maybe this post help you: Or your problem might be similar to this: If a child process writes large data to a pipe and the pipe buffer got full, then write to the pipe get blocked until parent process read t

Nim 2.0 -- thoughts

Your `type Path = distinct string` can be a good idea. Instead of creating a new types corresponding to a relative/absolute path, file/directory and symlink by inheriting from `Path`, generic distinct type might be better. Because if you create these types by inheritance, a number of types can b

Strange compilation error with Nim 1.4.6 on Mac

Maybe a clang vs GCC thing?

nimja; compiled and statically typed template engine (like twig or jinja2)

this is what unidecode does to the strings. The other option would be to port eg.: this php library:

Nim : Style insensitivity , snake_case , camelCase

What? Nimgrep supports it via its `-y` switch. Since a decade or so...

Nim : Style insensitivity , snake_case , camelCase

> Would it be possible to have a --styleCheck:coherent or something which > ensures that you use the same style for the same identifier in the same > module? I think it is `styleCheck:usages` which is new in 1.6 as @araq said.

nimja; compiled and statically typed template engine (like twig or jinja2)

should that not be: Ä,ä : ae Ö,ö : oe Ü,ü : ue ß : ss Run ?

Strange compilation error with Nim 1.4.6 on Mac

Sorry I can not change title. It's not a compilation error.

Strange compilation error with Nim 1.4.6 on Mac

Hi I have below code. It works on the Nim playground () but is failing on my local. If I remove proc x, it works. Wonder whether it's something with my installation or the specific Nim version I have. type A = ref object p: int

Nim : Style insensitivity , snake_case , camelCase

Python wont have Style insensitivity, thats the reason I have to use C++ names in PyQt ...

Nim : Style insensitivity , snake_case , camelCase

That would be `styleCheck:usages`, new in 1.6, I think?

Nim : Style insensitivity , snake_case , camelCase

Would it be possible to have a `--styleCheck:coherent` or something which ensures that you use the same style for the same identifier in the same module? Or even in your own project, but not necessarily the same as it was in the original definition? I sometimes mess up my casing, and while it wo

Nim : Style insensitivity , snake_case , camelCase

Nim is NOT like python...

Nim : Style insensitivity , snake_case , camelCase

Also consider using `styleCheck:usages` for big projects, the Nim compiler itself already uses more stricter style check: `--styleCheck:error` which enforces nep1. The style checking of the compiler now supports a `--styleCheck:usages` switch. This switch enforces that every sy

Nim : Style insensitivity , snake_case , camelCase

> For me and most of python devs, snake_case is a lot cleaner. I think it's **objectively** worse. Compare my_foo_bar = await other_baz_stuff(one_thing, another_thing) Run with myFooBar = await otherBazStuff(oneThing, anotherThing) Run Whil

Nim : Style insensitivity , snake_case , camelCase

As you mention, Nim is style insensitive. This means you can mix styles, which mostly comes in handy when importing a library from someone else and you want to use your own style. More often than not in my Python projects I would have imported two different libraries following different style-gu

nimja; compiled and statically typed template engine (like twig or jinja2)

a small update to nimja template engine : # slugify converts any string to an url friendly one. Removes any special chars and replaces non ASCII runes to their ASCII representation. slugify("Lession learned german umlauts: öüä")

Auto-free C pointer when Nim object gets GC

This example can only work in global scope. But interesting part is that nim generate call to `=destroy` for `distinct cptr[T]` type, so no nim wrapper object needed (will this support officially?). {.emit:""" #include typedef struct { int value; } Obj;

Child process shows exit code -1 when peeked, though it has definitely ended.

It's really hard to form any idea of what might be wrong without any code to peek at. If you have a minimal example that shows this behaviour it would help tremendously.