Ambiguous call from forward declared procedure created in a macro

[PMunch]

After a bug in nimsuggest was fixed that should keep nimlsp from crashing I tried to build nimlsp on the latest devel. This causes the error:

Error: ambiguous call; both nimlsp.isValid(data: JsonNode, schemaType`gensym1028144: type RequestMessage, traverse: bool, allowExtra: bool) [declared in /home/peter/.nimble/pkgs/jsonschema-0.2.0/jsonschema.nim(360, 12)] and nimlsp.isValid(data: JsonNode, schemaType`gensym1028145: type RequestMessage, traverse: bool, allowExtra: bool) [declared in /home/peter/.nimble/pkgs/jsonschema-0.2.0/jsonschema.nim(367, 12)] match for: (JsonNode, type RequestMessage)

The two procedures point to the macro code that generates them and one is only a forward declaration while the other is the procedure with the body.

[Araq]

The forward declaration uses a different gensym'ed symbol so the compiler thinks you introduced two separate procs.

[veksha]

Is it still relevant?

I see error while checking nimlsp.nim with nimlsp:
ambiguous call; both nimlsp.create(schemaType: typedesc[Diagnostic], therange: Range, severity: Option[system.int] or Option[system.float], code: Option[system.int] or Option[system.float] or Option[nimlsp.ResponseError], source: Option[system.string], message: string, relatedInformation: Option[seq[DiagnosticRelatedInformation]]) [proc declared in C:\Users\yura\.nimble\pkgs\jsonschema-0.2.1\jsonschema.nim(389, 12)] and nimlsp.create(schemaType: typedesc[Diagnostic], therange: Range, severity: Option[system.int] or Option[system.float], code: Option[system.int] or Option[system.float] or Option[system.string], source: Option[system.string], message: string, relatedInformation: Option[seq[DiagnosticRelatedInformation]]) [proc declared in C:\Users\yura\.nimble\pkgs\jsonschema-0.2.1\jsonschema.nim(382, 12)] match for: (typedesc[Diagnostic], Range, Option[system.int], Option[system.int], Option[system.string], string, Option[seq[DiagnosticRelatedInformation]])

it compiles correctly of course. so can it be bug in nimsuggest module that is used by nimlsp?

[PMunch]

Yeah that sounds like a nimsuggest bug, which version of Nim sources did you use when building nimlsp?

[veksha]

Yeah that sounds like a nimsuggest bug, which version of Nim sources did you use when building nimlsp?

Nim Compiler Version 1.6.5 [Windows: amd64]
Compiled at 2022-04-21
dc4cc2d (commited 27 days ago)

[veksha]

same with last devel nim sources.