fix hcr test

Author: timotheecour

tests/dll/nimhcr_0.nim

@@ -1,4 +1,4 @@
 
 let g_0 = 1000 # new value! but also a "new" global :)
 
-proc getInt*(): int = return g_0
+proc tgetInt*(): int = return g_0

tests/dll/nimhcr_0_1.nim

@@ -3,7 +3,7 @@ import hotcodereloading
 
 let g_0 = 42 # lets start with the ultimate answer
 
-proc getInt*(): int = return g_0
+proc tgetInt*(): int = return g_0
 
 programResult = 0 # should be accessible
 

tests/dll/nimhcr_0_2.nim

@@ -9,7 +9,7 @@ echo "   0: I SHOULDN'T BE PRINTED!"
 
 var g_0 = 0 # changed value but won't take effect
 
-proc getInt*(): int = return g_0 + g_1 + f_1()
+proc tgetInt*(): int = return g_0 + g_1 + f_1()
 
 beforeCodeReload:
   echo "   0: before - improved!" # changed handlers!

tests/dll/nimhcr_0_3.nim

@@ -16,4 +16,4 @@ afterCodeReload:
   echo "   0: after - closure iterator: ", c()
   echo "   0: after - c_2 = ", c_2
 
-proc getInt*(): int = return g_1 + g_2.len
+proc tgetInt*(): int = return g_1 + g_2.len

tests/dll/nimhcr_0_4.nim

@@ -5,7 +5,7 @@ import nimhcr_1 # only importing 1
 
 let g_0 = 1000 # new value! but also a "new" global :)
 
-proc getInt*(): int = return g_0
+proc tgetInt*(): int = return g_0
 
 proc makeCounter*(): auto =
   return iterator: int {.closure.} =

tests/dll/nimhcr_0_5.nim

@@ -1,2 +1,2 @@
 
-proc getInt*(): int = return 42 # back to the answer...
+proc tgetInt*(): int = return 42 # back to the answer...

tests/dll/nimhcr_0_6.nim

@@ -1,4 +1,4 @@
 
 let g_0 = 1000 # new value! but also a "new" global :)
 
-proc getInt*(): int = return g_0
+proc tgetInt*(): int = return g_0

tests/dll/nimhcr_integration.nim

@@ -79,7 +79,7 @@ After instrumenting code, the stacktrace actually points to the call to `check m
 ## A few files can be updated by calling `update` for each of their indexes
 ## and after that with a single call to `compileReloadExecute` the new version
 ## of the program will be compiled, reloaded, and the only thing the main module
-## calls from `nimhcr_0.nim` (the procedure `getInt` proc) is called for a result.
+## calls from `nimhcr_0.nim` (the procedure `tgetInt` proc) is called for a result.
 ##
 ## This test is expected to be executed with arguments - the full nim compiler
 ## command used for building it - so it can rebuild iself the same way - example:
@@ -91,7 +91,7 @@ After instrumenting code, the stacktrace actually points to the call to `check m
 
 import os, osproc, strutils, hotcodereloading
 
-import nimhcr_0 # getInt() - the only thing we continually call from the main module
+import nimhcr_0 # tgetInt() - the only thing we continually call from the main module
 
 proc compileReloadExecute() =
   # Remove the `--forceBuild` option - is there in the first place because:
@@ -121,7 +121,7 @@ proc compileReloadExecute() =
     quit 1
   echo "main: hasAnyModuleChanged? ", hasAnyModuleChanged()
   performCodeReload()
-  echo "              The answer is: ", getInt()
+  echo "              The answer is: ", tgetInt()
 
 # there are 3 files and all of them start from their 1st version
 var vers = [1, 1, 1]