nim-gdb: Undefined command: "import"

Isn't the point of `source` to run a shell script in the current shell? I have never seen a python script run with `source` before. I created this simple script as a test: #!/usr/bin/env python echo Hello print("World") Run When I `source test.py` with bash I

Idea: Marketing Nim to Organizations

> I still have not found how to edit this wiki. Do you not see an [Edit](https://github.com/nim-lang/Nim/wiki/Organizations-using-Nim/_edit) button?

Idea: Marketing Nim to Organizations

Is the list still accurate? A few months ago I picked Userify at random and there's no mention of Nim in any of the job listings. There's also almost no hits for Nim the programming language using various job search engine.

This Month with Nim: October 2022

Here are some projects our community did in October: * * * If you want to include your project for the next month (it doesn't have to be a new project), follow the instructions [here](https://github.com/beef331/website/issues/new?

Idea: Marketing Nim to Organizations

Still, this is my personal opinion, so please don't be negative about it.

nim-gdb: Undefined command: "import"

The `source` command is shell-dependent, not OS dependent. By default, MacOS uses zsh, which does have the `source` command. If you use /bin/sh, it might point to /bin/dash instead, which does not have the `source` command. The issue with MacOS though, is that it is not recommended to use source

NimEdit: can it be made compilable with Nim 1.6.8?

Because it: * is written in Nim * is lightweight * is SDL2 based * I like the concept * looks nice to me

Looping Assertions

Compile with `--assertions:off --overflowChecks:off`. The array bounds checks can sometimes be optimized out by the C(++) backend.

Looping Assertions

Not true, they are only turned off in danger mode. Maybe you can define your own iterator that does `push checks: off` for the element access.

Looping Assertions

> But it'll then perform a bound check at the beginning of each loop, and a > overflow check at each end, which is no more efficient than assertions, and > still needed to be turned off. Bound checking and most assertions are turned off in release mode

Looping Assertions

> But it'll then perform a bound check at the beginning of each loop, and a > overflow check at each end, which is no more efficient than assertions, and > still needed to be turned off. Bound checking and most assertions are turned off in release mode

Looping Assertions

Seq with unchangeable length can be implemented as `type FixedSeq[T] = distinct seq[T]` with only certain overloads allowed, like `[]=` but not `add`

Looping Assertions

Oh I see. Even if loop though `items`, boundary and overflow checks still exist. But I still want alt `seq` with unchangable length. Arrays do have fixed length, but must be determined at compile-time.