Type Mismatch incomplete signature on error

[SrMordred]

Type mismatch error output shows incomplete type signature, making it harder to debug.

Example

Basic nimble package file +

requires "nim >= 1.0.0"
requires "jester"
requires "ws"

Source

import jester
import ws

routes:
    get "/":
        var ws = await newWebSocket(getNativeReq(request))

Current Output

nim_error/src/nim_error.nim(6, 36) Error: type mismatch: got <Request

but expected one of: 
	proc newWebSocket(req: Request): Future[WebSocket]
	first type mismatch at position: 1
	required type for req: Request
	but expression 'getNativeReq(request)' is of type: Request

Expected Output

nim_error/src/nim_error.nim(6, 36) Error: type mismatch: got <httpbeast.Request

but expected one of: 
	proc newWebSocket(req: Request): Future[WebSocket]
	first type mismatch at position: 1
	required type for req: asynchttpserver.Request
	but expression 'getNativeReq(request)' is of type: httpbeast.Request

Possible Solution

Don´t know :).
Apparently this only occurs with external packages. (Local file modules show the complete signature "module.type")

$ nim -v
Nim Compiler Version 1.0.99

[Araq]

Such a weird thing. Are you sure it's not caused by something like output redirections? (From Nimble or other tools...)

[SrMordred]

nim c -r src/nim_error.nim give me the same output.

[Araq]

This does compile for me, so please setup a real test case which we can reproduce.

[SrMordred]

I´m sorry. I should had informed at first: this fail on linux, because Jesters changes the Request type from asynchttpserver to httpbeast on linux only.

[disruptek]

I read the error message, I read what you wrote, and I read the jester source and everything I read appears to be consistent. If you want to use a Request type that will match the required argument signature for the ws factory procedure newWebSocket, then you will need to compile with the -d:useStdLib so that the jester's Request used is the one from the standard library as required.

[SrMordred]

@disruptek My complain is not about the 'error' with Jester. (yes, I already solved it with the d:useStdlib :) )
Its about the error message not being clear about what happened:

required type for req: Request
but expression 'getNativeReq(request)' is of type: Request

Since it didn't prefixed the type with the module , it was a confusing error ( but my type IS Request :P )

If you simulate this problem on a local project, it displays the error correctly:
ex:

required type for myvar: Module1.TypeA
but expression ' myvar ' is of type: Module2.TypeA

Looks like imported packages from another package don´t show the module prefix.

[disruptek]

You're right of course; I'm an idiot. I confused this for a new issue when I saw Araq's comment in my email. 😁