Arne Döring

Araq: well I don't think that's necessary. The macro can check if it is based on a ref type or anything else. My original implementation just didn't care for ref...

At first sight I thought this would be the same thing as https://github.com/nim-lang/Nim/issues/11155, but it isn't. The ``convert`` symbol is resolved in ``test``, which is defined in `a.nim`, a totally...

The example is a bit verbose, I could boil it a bit down if that helps to fix the bug. It seems like varargs is causing the problem, because without...

This is not only a problem with `object`. Basically any generic argument or concept causes weird internal errors. I tried also with ``SomeInteger`` and ``typedesc`` instead of ``object``. ``SomeInteger`` has...

comment from Araq: This should work, and private sort should not bind to anything from instantiation context. ```nim proc privateSort(...) proc sort[T]() = privateSort(...) # delegate bind privateSort

Unsigned integer have modulo arithmetic. In modulo 256 arithmetic, `-1` and `255` are equivalent. So in my experience it makes sense that a conversation to a type with modulo arithmetic...

> I think the issue is that `openArray` is not a view, it's more like an `interface-hardcoded-concept-meets-view-thingy`. I think first step is figuring out what `openArray` actually means, then we...

I have not touched this code in years. So technically this is not actively maintained anymore. I do not intend to fix it for new breaking changes in Nim, as...

If you report on the error that you got. I might look into it. No guarantees though.

@tomangelo2 Installing `.dll` files is something that doesn't sound very platform independent. What might work though, is if you want c++ support, is to deliver a c++ compiler like clang,...