Nim: A warning for unused but conflicting procs would be nice

Created on 17 Sep 2017  路  5Comments  路  Source: nim-lang/Nim 
proc x(): int = 7
proc x(): string = "strange"

#var h: int = x() # does not compile
# but why is there no warning for the two procs?
# As they make no sense. (Reported by a gintro user)
Easy Error messages Showstopper
Source
picture StefanSalewski

Most helpful comment

Well, I want to implement return type overloading eventually. Should we track this as a separate feature issue?

picture zah on 23 Apr 2018
👍2

All 5 comments

@Araq Should https://github.com/nim-lang/Nim/commit/13c6037fd4119fbc67b31524bfb271652cc3df84 be merged into devel?

dom96 picture dom96 on 19 Sep 2017

Can't, it needs to be fixed slightly differently.

Araq picture Araq on 20 Sep 2017
👍1

This is actually implemented, but doesn't work as expected. Since this is annoying me on a personal level, showstopper bug.

Araq picture Araq on 21 Apr 2018

Well, I want to implement return type overloading eventually. Should we track this as a separate feature issue?

zah picture zah on 23 Apr 2018
👍2

Return type overloading would be an RFC.

Araq picture Araq on 23 Apr 2018
Was this page helpful?
0 / 5 - 0 ratings

Related issues

anthraxx picture anthraxx  路  26Comments
Araq picture Araq  路  74Comments
dom96 picture dom96  路  47Comments
niv picture niv  路  40Comments
kaushalmodi picture kaushalmodi  路  25Comments