Re: module name collision across nimble packages

2018-04-03 Thread Araq
Indeed, you cannot use `std.times.callFun()` as an expression. Nim is not D, I'm sorry.

Re: module name collision across nimble packages

2018-04-03 Thread timothee
argument for dots: it's nice that declaration matches usage: std.times.callFun() ; whereas we can't use: std/times.CallFun()

Re: module name collision across nimble packages

2018-04-03 Thread Araq
I don't like the dots and think we should deprecate them.

Re: module name collision across nimble packages

2018-04-01 Thread timothee
thanks! actually, import std/times is allowed but not std.times ; shouldn't both be supported?

Re: module name collision across nimble packages

2018-03-31 Thread dom96
Good questions. Most of them are answered by Nimble's readme, but the packages readme should also contain this info (PRs welcome). > Q1 :what happens if 2 nimble packages with same name are published to nimble? > eg: > [https://github.com/ivankoster/protobuf-nim](https://github.com/ivankoster/p

module name collision across nimble packages

2018-03-31 Thread timothee
Q1 :what happens if 2 nimble packages with same name are published to nimble? eg: [https://github.com/ivankoster/protobuf-nim](https://github.com/ivankoster/protobuf-nim) [https://github.com/PMunch/protobuf-nim](https://github.com/PMunch/protobuf-nim) I don't see any package name uniqueness co