Andreas Rumpf

@ringabout @metagn Please bisect it.

It's not "obviously wrong", closure environments can be self-referencing which is why you need a cycle collector for them. This is even more true for the so called "up" pointers...

> Also the pointer type mismatch kinda hints that this particular line is fishy at least? Sure, yes.

*shrug* And for ``nim cpp`` it can work out...

It doesn't matter, if you use ``exportc`` or ``emit`` or ``header`` there is a limit to what we can check before we hit the C compiler / linker. Eventually we...

> This is so the bindings for the typeclasses in the constraint don't leak into the entire candidate, i.e. the binding for T: SomeInteger should not be used for all...

Can you undraft this? Every little progress on this front is greatly appreciated.

``some(a[0])`` produces an Option[int], not an Option[lent int], this should produce a type mismatch error.

Thanks! It is much better this way.

Don't close this.