On Saturday, July 27, 2019 7:12:32 AM MDT evilrat via Digitalmars-d-learn
wrote:
> On Saturday, 27 July 2019 at 12:48:12 UTC, BoQsc wrote:
> > I seem to be doing something wrong, the result is the same.
> >
> >> otherFile.d(8): Error: only one main, WinMain, or DllMain
> >> allowed. Previously
On Saturday, 27 July 2019 at 17:13:45 UTC, Adam D. Ruppe wrote:
If you change that to just plain `return NodeList(a, b);`,
while keeping the first line, it will compile too.
The reason here is when you return and construct together, it
constructs it in-place. But if you put it in a local
On Saturday, 27 July 2019 at 16:59:44 UTC, Newbie2019 wrote:
auto list = NodeList(a, b);
If you change that to just plain `return NodeList(a, b);`, while
keeping the first line, it will compile too.
The reason here is when you return and construct together, it
constructs it
I think this is a bug.
If I return a struct more than one times, will throw this error.
If I return once, every thing is ok.
https://run.dlang.io/is/T4kWKM
ref auto getList() return scope {
if( i ) return NodeList(null); // remove this line will fix
this error
On Saturday, 27 July 2019 at 11:54:09 UTC, BoQsc wrote:
I would like to make sure that function in module that I have
won't be imported, is this possible to achieve?
In general, make the function private.
But indeed, on your case, it is a terrible idea to define a
main() function in a module
I would like to make sure that function in module that I have
won't be imported, is this possible to achieve?
Test subject:
mainFile.d
import otherFile;
void main(){
}
otherFile.d
import std.stdio : writeln;
import std.file : mkdir;
int main(){
writeln("test ");
