Skip to content

Comments

Fix genCmain code to remove ambiguity of &main expression#2

Closed
9rnsr wants to merge 1 commit intomasterfrom
fix_main
Closed

Fix genCmain code to remove ambiguity of &main expression#2
9rnsr wants to merge 1 commit intomasterfrom
fix_main

Conversation

@9rnsr
Copy link
Owner

@9rnsr 9rnsr commented Sep 9, 2013

It was introduced by dlang#2476, but the expression &main which is implicitly
inserted would conflict with two extern(C) and (D) "main" functions in
user module.

Instead, separate the entry-point code in the hidden module __entrypoint.d

It was introduced by pull#2476, but the expression `&main` which is implicitly
inserted would conflict with two extern(C) and (D) "main" functions in
user module.

Instead, separate the entry-point code in the hidden module __entrypoint.d
@9rnsr 9rnsr closed this Sep 9, 2013
9rnsr added a commit that referenced this pull request Nov 30, 2013
…ple not type Foo

Even if a variable has no valid context, it would be either:

1. a part of compile time evaluated expression, which is used as unreal context.
    enum x = Type.fieldvar.sizeof;
    // It's legitimate expression so fieldvar is not evaluated
    // in runtime.

2. or an invalid field access without valid 'this', in runtime evaluated expression.
    int y = Type.fieldvar;
    // It's invalid expression so fieldvar access has no valid 'this'.

For the case #2, it will be an error by `checkRightThis` later. Therefore `getRightThis` should not make it an error.
9rnsr pushed a commit that referenced this pull request Sep 4, 2014
9rnsr pushed a commit that referenced this pull request Aug 9, 2016
Trivial: switch to Ddoc module comment #2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant