Strange behavior of con with dot operator
test.nim
1. let f = open("test.txt", fmWrite)
2. f.write("text")
3.
4. import json
5. json.parseFile(
Launch nimsuggest:
nimsuggest --v2 --debug --stdin test.nim
Empty output when issuing the following commands:
con test.nim 2 8
con test.nim 5 5
Procs definitions output when issuing the following commands:
con test.nim 2 2
con test.nim 5 15
nimsuggest --v
Nim Compiler Version 0.16.1 (2017-04-20) [Windows: i386]
Copyright (c) 2006-2017 by Andreas Rumpf
git hash: 5a4c06dbdce20a8966742d75ea6e5e227c6d1f14
active boot switches: -d:release --gc:markAndSweep
According to the documentation of nimsuggest:
...this one is meant to be used after the user has typed an opening brace to start typing parameters.
Edit: Another con issue with a nested invocation context. test.nim
1. proc test1(x1, y1: int): int = x1
2. proc test2(x2, y2: float): int = y2.int
3.
4. test1(1, test2(
Same proc prototype (test1) when issuing the following commands:
con test.nim 4 6
con test.nim 4 15
Are you sure you didn't made an mistake when you requested the con of json.parseFile. Because you requested at 5, 5 and nothing happend but it appeared when you requested it at 5, 15 which is the correct behavior(5, 5 is inside the json but 15 is just behind the bracket).
I've gone through all of these bugs using Nim bleeding edge(from yesterday) and the first with f.write("text") still doesn't work and the example with the nested calls also still doesn't work. When requesting at the right position the second example works. E.g. my editor shows the signature for json.parseFile.
EDIT: I wrote some nonesense here a few minutes before, please forget about this, if you read it