Channels documentation

I could have got that idea from an old forum post. Glad to hear that there's no present incompatibility.

Channels documentation

You mean the `spawn` in the threadpool module? I don't know of any incompatibility between it and the new channels. If it's being considered for deprecation, that's news to me...

Adding Nim to System default base

Good day, Yes, sometimes the obvious path is the last to think of. Checking the pkgbuild by Arch community clarifies the question. Thus, this could be marked as [solved]. Thanks again @SolitueSF. Regards, noxnivi

How is default argument before code line one?

This is actually fixed but behind a switch (maybe because it has bugs): {.experimental: "flexibleOptionalParams".} template h( foo = "", bar : untyped ) = echo foo bar h "foo" : echo "bar" h: echo "foo" Run

GUI: Nim + QML unable to compile

Good day @Yardanico, True. It's nim c. My bad. I've been already through many Nim tutorials (those two you mention I've already went through several weeks ago. Now I'm at this: . I've done some Nim in Action stuff too, but seems examples there don't wor

Adding Nim to System default base

Thanks. Will do check that! Didn´t think about it Again, thanks a lot. Regards, noxnivi

Adding Nim to System default base

just look what nim pkgbuild from arch does. or any other distro. just moving binaries isn't really enough.

GUI: Nim + QML unable to compile

It's `nim c file.nim`, `c` means `compile` and it's a subcommand, not an argument.

GUI: Nim + QML unable to compile

Good day, I finally decided to go with Nim + QML for the GUI using nimqml. Mostly because I want the ability of setting up a GUI and then decide if I use Python or Nim for the core. I think I tried all available GUI kits without any success, though it might be also due to lack of research on th

Adding Nim to System default base

Good day, I've been installing Nim from source lately and was wondering if I could add it as part of the base system by adding it to the proper /bin folder (/bin, /usr/bin, /sbin, /usr/sbin... whatever]. So my question is, from the source installed Nim, would it be enough to move all files from

Small improvement discussion: Use `let` to lock variable previously declared as `var`

no, it doesnt, its only broken as procedure parameter, everywhere else you can "redeclare" it.

How is default argument before code line one?

what? also, your particular case can be fixed by making explicit overload without `foo` parameter. template h( foo: string, bar : untyped ) = echo foo bar template h(bar: untyped) = h "", bar Run

How is default argument before code line one?

How is way on default argument before code line one (should get worked anyway) ? Illustrated; template h( foo = "", bar : untyped ) = echo foo bar h "foo" : echo "bar" h: echo "foo" Run Please solve me out, thanks

Small improvement discussion: Use `let` to lock variable previously declared as `var`

What about allowing `_` to be able to shadow itself. Right now it acts like any other identifier, meaning you can't redeclare it.

Small improvement discussion: Use `let` to lock variable previously declared as `var`

> Now I am wondering- could the shadowing syntax be implemented with a macro? > Likely not, correct? Challenge accepted ;-) import std/macros import macroutils # https://github.com/PMunch/macroutils macro blockinit(letSection: untyped): untyped = letSection.expe

Show Nim: Guzba and I are publishing YouTube videos discussing our work in Nim

I will watch for sure ! You two are doing great for the Nim ecosystem :)

Channels documentation

I'm actually thinking of going with StashTable instead:

Small improvement discussion: Use `let` to lock variable previously declared as `var`

I learned the hard way to occasionally not let the ugliness get in the way of the usefulness :)

Small improvement discussion: Use `let` to lock variable previously declared as `var`

This is really simple and useful. Nice

Small improvement discussion: Use `let` to lock variable previously declared as `var`

Thank you, everyone, for sharing your ideas!!! Personally, I like the non-indented shadowing more. Sure, the block-based approach gives you protection from abusing the feature, but it also forces you to put dependencies of the computation into a block. You, the programmer, should decide if you