diff options
author | Vindaar <basti90@gmail.com> | 2019-08-27 22:23:47 +0200 |
---|---|---|
committer | Andreas Rumpf <rumpf_a@web.de> | 2019-08-27 22:23:47 +0200 |
commit | eff0837ff40e4a5f5659ff02a56d9936bcbd7bcd (patch) | |
tree | 6b189c3ed12d58b63b015bf86e84d5333c4c8756 /koch.nim | |
parent | 00d46ca1c04935b7b4fe16e7f72204b46f5651fa (diff) | |
download | Nim-eff0837ff40e4a5f5659ff02a56d9936bcbd7bcd.tar.gz |
fixes #12015 by also checking kind of `typeNode` (#12016)
* fixes #12015 by also checking kind of `typeNode` If a tuple field is aliased it'll appear the same as a ref type in a call to `getType` if only for the kind of the resulting `NimNode` is checked (that is a `nnkBracketExpr`) * fix test case due to #12017 and add more realistic test case Adds an additional test case, which includes generics and is closer to the real failure I encountered * remove previous fix and fix differently after all The previous fix was incomplete, because it failed for generics. Note that the `of "tuple"` is not actually needed, the `nnkBracketExpr` branch in the `else` branch would catch it too, but I decided to introduce it for clarity. However, the latter is actually needed, because it seems for aliases of `seq` we end up in it. * update comment about global `%` proc in json test
Diffstat (limited to 'koch.nim')
0 files changed, 0 insertions, 0 deletions