Fix range type construction in the VM (#9205)
The `range[X,Y]` representation is wrong, we use `range[X .. Y]` instead. Fixes #9194
This commit is contained in:
parent
dad290accb
commit
8a1055adce
2 changed files with 29 additions and 2 deletions
20
tests/macros/t9194.nim
Normal file
20
tests/macros/t9194.nim
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
discard """
|
||||
output: '''
|
||||
range[0 .. 100]
|
||||
array[0 .. 100, int]
|
||||
'''
|
||||
"""
|
||||
|
||||
import macros
|
||||
|
||||
type
|
||||
Foo1 = range[0 .. 100]
|
||||
Foo2 = array[0 .. 100, int]
|
||||
|
||||
macro get(T: typedesc): untyped =
|
||||
# Get the X out of typedesc[X]
|
||||
let tmp = getTypeImpl(T)
|
||||
result = newStrLitNode(getTypeImpl(tmp[1]).repr)
|
||||
|
||||
echo Foo1.get
|
||||
echo Foo2.get
|
||||
Loading…
Add table
Add a link
Reference in a new issue