Mirror of forum.nim-lang.org

1394 :: Warning: method has lock level <unknown>, but another method has 0 [LockLevel]

• mr_july (orginal) [2015-07-02T09:51:26+02:00] view original

  Hallo,

  the following code

  import json
  
  type
    A = ref object of RootObj
    B = ref object of A
  
  method test(x: A): string =
    "got A"
  
  method test(x: B): string =
    discard parseJson("{test: 1}") # this line produces warning
    "got B"
  Run

  produces the warning:

  
  test.nim(10, 8) Warning: method has lock level <unknown>, but another method has 0 [LockLevel]
  Run

  What's going wrong here and how to get rid of this? Thanks in advance!

---

• Araq (orginal) [2015-07-02T10:51:06+02:00] view original

  Either use --warning[LockLevel]:off or fix the json library so the compiler knows parseJson doesn't lock.

---

• Varriount (orginal) [2015-07-02T20:38:55+02:00] view original

  How would that be done?

---

• Araq (orginal) [2015-07-02T23:05:35+02:00] view original

  Usually by adding .benign to the forward declarations in json.nim.

---

• geezer9 (orginal) [2016-11-17T16:54:39+01:00] view original

  Also you can stick the pragma {.warning[LockLevel]:off.}

  inside the effected proc as its first line.

  I also noticed that having a proc field in the method receiver seemed to be related to the problem. Anyway, adding the pragma {.locks:0.} to the declaration of the field got rid of one of these warnings - but did not seem to work on others.

  Oh well...

  BTW it is .locks and not .lock

---

• ninovanhooff (orginal) [2024-03-18T16:32:26+01:00] view original

  Hello from the future!

  I'm using Nim 1.6 at the moment, moving to 2.0 soon.

  I'm targeting a single core system without threading and would like to turn off the locklevel warning project-wide.

  1. Is it true that this whole concept is gone or deprecated in v2?
  2. This doesn't work when I stick it in config.nims on 1.6.16:

  
  --warning[LockLevel]:off
  Run

  or

  
  switch("warning[LockLevel]","off")
  Run

  Both give the same result: invalid command line option: '--warning[LockLevel]' Instead I have been adding {. push warning[LockLevel]:off.} to any file where necessary. Is there a better way to do this globally?

---

• konradmb (orginal) [2024-03-26T15:39:11+01:00] view original

  1. Yes, lock levels now do nothing on 2.0: https://github.com/nim-lang/Nim/pull/20539
  2. --warning[LockLevel]:off won't work, because config.nims should be a valid NimScript. You can replace it with switch("warning","[LockLevel]:off"). Tested, works for me.

  Proper solution:

  Create a file nim.cfg in your project root dir and put --warning[LockLevel]:off in it (actually manual tells that --warning:LockLevel:off is valid one). You can also name it myprogram.nim.cfg to apply it only to myprogram.nim (more in docs).

---