cooldome

Results 24 comments of cooldome

Crash of compiler on array type check

Small note: StringArray[N:int] or StringArray[N] does not make difference, compiler crashes in exactly the same way

Crash of compiler on array type check

Thanks Zah for clarification

Crash of compiler on array type check

I though of it once again, shouldn't this work? ``` type StringArray[N] = array[N, string] let a = ["one", "two"] echo a is StringArray` ``` It crashes the same way...

execution traces (eg for code coverage, debugging, introspection, profiling)

My idea is to upgrade existing https://nim-lang.github.io/Nim/manual_experimental.html#term-rewriting-macros functionality to make things like coverage, extra debug reports possible. Effectively term rewriting macro should be able to find and rewrite any proc,...

typetraits: implements `value in type`

To be honest I don't think it a good idea to mix types and runtime values this way. IMO, constants are much better for your use case: ```nim const AllowedPort...

typetraits: implements `value in type`

Agree, last example is convincing. #15232 is more appealing

`=default` type bound operator to override `default` and `var` initialization

Why not `=init(x: var T)` as proposed in #252?. It is more efficient, no extra move/copy operation required

All let {.compileTime.} constructs can now be const instead

I see little value, lots of changes required but nothing that can't be done today will be made possible.

[RFC] dependent types, restricted types or generalization of the range types

Hi Mratsim, I can't transfer it either. RFCs repo is not in the list of for transfer. Can I somehow give you the permission?

Making Nim's strings Copy-On-Write (COW)

I had a read, feels that `sink T`, `lent T`, `var T` and `openarray[T]` combined with https://github.com/nim-lang/RFCs/issues/178 is more generic solution to the optimization/performance problems. It does feel odd that...