nimsuggest output differ much from nim compiler

[Q-Master]

Nim Version

Nim Compiler Version 2.2.2 [Linux: amd64]
Compiled at 2025-02-06
Copyright (c) 2006-2025 by Andreas Rumpf

git hash: 6c34f62
active boot switches: -d:release

Description

nimsuggest via nim langserver shows an error Redefining UserAuth: line 10, column 3 in this code using my nim library nimble install packets

import std/[parseopt]
import packets/packets
import packets/json/serialization


var uids: seq[string]


packet UserAuth:
  var userId* {.asName: "user_id".}: string
  var token*: string
  var ts: int64


proc main() =
  for kind, key, value in getopt():
    case kind
    of cmdEnd: break
    of cmdShortOption, cmdLongOption:
      discard
    of cmdArgument:
      uids.add(key)


when isMainModule:
  main()

but nim compiles this code and it works perfect.

Current Output

Expected Output

Known Workarounds

No response

Additional Information

No response

[foxoman]

You defined this error in /internal/packet.nim file in your library, line 66:

  if packetCache.hasKey(packetname):
    error("Redefining the " & packetname, body)

On the first start of nimsuggest, it start fresh and no cache of the keys, but on later check it will generate they key when analyzing your macro, while compiling it will start fresh and will compile fine.

[Q-Master]

@foxoman yep, this code in my lib is about protecting from same DSL names. I don't really understand why should it reparse the code with some cached data? Especially if there are macros there which are definitely generating some additional code.