unique refs > `isolate`

> "Container[ref T] is isolatable when the container can only be moved" That sorta makes sense. Hmmm, interesting paper was just on HN on this topic: No idea how good it is yet, but I like its discussing isolation.

feasible lib(s) to do FFT on image with minimal dependencies?

I use windows 10 64 bits. In my case, I want to check whether an image is blurred or not. There are some steps according to 1. read image into f(x,y). In fact there is no i

unique refs > `isolate`

Yeah ... "[x] make the mechanism use some sendable type annotation"

unique refs > `isolate`

> A sendable type is a type with a disabled =copy operation. This implies > Isolated[T] is itself sendable and can be used to create more complex > isolated data structures. I'm lost here. How does copy operator invalidate isolate[T] guarantees? Wouldn't copyable data types be even easier to se

Declaring an uninitialized seq & avoid unnecessary zero-mem's

Depends on the use case, when you build up the custom seq directly there would be no copying.

Declaring an uninitialized seq & avoid unnecessary zero-mem's

> No, these only mean that you need to use a custom seq. But I agree it's not > ideal. all other idiomatic nim code uses a seq -> one would have to copy from custom seq to seq -> defeats the purpose of avoiding zero:ing.

Announce: LimDB 0.3.0 Now with types & block-syntax transactions

Thanks! I realized that was a core LMDB feature that needed a Nimish interface.

Is there a way to tell the compiler to include/export unused functions

What does it mean to export a generic proc? Do you instantiate it infinite times, once for every possible type?

Declaring an uninitialized seq & avoid unnecessary zero-mem's

> these prevent writing code that is possible to write efficiently in other > languages. No, these only mean that you need to use a custom `seq`. But I agree it's not ideal.

Announce: LimDB 0.3.0 Now with types & block-syntax transactions

Nice! Transaction with multiple DB looks cool!