zielmicha / reactor.nim

Asynchronous networking engine for Nim
https://networkos.net/nim/reactor.nim/doc/
MIT License
108 stars 6 forks source link

Cannot Instantiate: 'T' #23

Open ImVexed opened 5 years ago

ImVexed commented 5 years ago

Nim Compiler Version 0.19.4 [Linux: amd64]

Fresh nimble install of reactor, had to manually clone libuv and reset to specified hash.

Upon compilation of sample program:

import reactor/tcp, reactor/async

proc main() {.async.} =
    let server = await createTcpServer(5000)
    asyncFor conn in server.incomingConnections:
        # handle incoming connection
        await conn.output.write("hello")

when isMainModule:
    main().runMain

I get:

nim c -r --threads:on --nilseqs:on tcp_client.nim
Hint: used config file '~/.choosenim/toolchains/nim-0.19.4/config/nim.cfg' [Conf]
Hint: system [Processing]
Hint: tcp_client [Processing]
Hint: tcp [Processing]
Hint: util [Processing]
Hint: future [Processing]
Hint: macros [Processing]
Hint: bytes [Processing]
Hint: endians [Processing]
Hint: strutils [Processing]
Hint: parseutils [Processing]
Hint: math [Processing]
Hint: bitops [Processing]
Hint: algorithm [Processing]
Hint: unicode [Processing]
Hint: base64 [Processing]
Hint: views [Processing]
Hint: lang [Processing]
Hint: loop [Processing]
Hint: uv [Processing]
Hint: errno [Processing]
Hint: posix [Processing]
Hint: build [Processing]
Hint: os [Processing]
Hint: times [Processing]
Hint: options [Processing]
Hint: typetraits [Processing]
Hint: strformat [Processing]
Hint: ospaths [Processing]
Hint: osproc [Processing]
Hint: strtabs [Processing]
Hint: hashes [Processing]
Hint: streams [Processing]
Hint: cpuinfo [Processing]
Hint: linux [Processing]
Hint: uvutil [Processing]
Hint: ipaddress [Processing]
Hint: sequtils [Processing]
Hint: iterate [Processing]
~/.nimble/pkgs/reactor-0.5.0/reactor/ipaddress.nim(196, 12) template/generic instantiation from here
~/.nimble/pkgs/collections-0.5.2/collections/iterate.nim(46, 20) Error: cannot instantiate: 'T'
zielmicha commented 5 years ago

Probably some versioning conflict again... Will fix this soon.