fix Issue 11246 - [REG 2.063] Struct initialized in constructor is destroyed first
fix Issue 11261 - Can't infer types without explicit slice in foreach
Merge pull request #2665 from 9rnsr/fix9665

Issue 9665 - Structure constant members can not be initialized if have opAssign
Merge pull request #2668 from 9rnsr/fix11261

[REG2.064a] Issue 11261 - Can't infer types without explicit slice in foreach
fix Issue 11271 - auto ref opAssign + destructor + struct literal fails
fix Issue 11265 - Segfault while calling instance method of class defined inside struct

The regression was introduced by the commit:
https://github.com/D-Programming-Language/dmd/commit/671b7c20b96b580ee1dc2b3f5e3ee66c63d079b6#diff-43282ebf5a2de5fdbcb3b5083ddf949dR147

vtbl[] calculation is essentially unrelated to the class instance size.
So, just only once initializing of vtbl[] and running semantic on member
functions is sufficient.
fix Issue 11215 - `inout` lose enclosing `shared` on resolution
Merge pull request #2669 from 9rnsr/fix11271

[REG 2.063] Issue 11271 - auto ref opAssign + destructor + struct literal fails
Merge pull request #2670 from 9rnsr/fix11265

[REG2.064a] Issue 11265 - Segfault while calling instance method of class defined inside struct
Merge pull request #2630 from WalterBright/fix3753

fix Issue 3753 - ICE(eh.c): Related to exception handling and alloca.
fix Issue 11225 - Module dependency cycle causes import statements inside typeof() expressions inside templates to fail
Merge pull request #2671 from 9rnsr/fix11225

[REG2.061] Issue 11225 - Module dependency cycle causes import statements inside typeof() expressions inside templates to fail
fix Issue 10684 - Refused array op with array literal

Accept array literals as the operand of array-ops.

---

Since, array-ops had required explicit slice to the array literal operands,
eg. `a[] = [1,2][] + c[];`

By the commit:
https://github.com/9rnsr/dmd/commit/f703c5c6551affddd9213f759657a2b3e391b935
now the redundant slice operators at the right side of an array literal is
entirely removed - `[1,2,3][][]` is rewritten to `[1,2,3]`.

Although it has broke existing code using array-ops, I still cannot think
the optimization was incorrect.

On the other hand, I could not find the description about the necessity of
explicit slice on array literal from the language spec.
http://dlang.org/arrays.html#array-operations
It looked to me that is just an implementation-specific restriction.

So, I implemented this as the easiest way to fix the issue.
Disable enhancement feature 7444

Existing issues:

http://d.puremagic.com/issues/show_bug.cgi?id=11276
To enforce slice + assign syntax `a[] = b[]` may cause problems with generic code.

http://d.puremagic.com/issues/show_bug.cgi?id=11244
A case yet difficult to make it clear - combination with operator overloading.
add configuration files
Merge pull request #2674 from WalterBright/add-ini

add configuration files
Merge pull request #2667 from eco/env64-linkcmd

Support LINKCMD for Win64 Environment64
add missing config files
Merge pull request #2676 from WalterBright/add-ini2

add missing config files
Merge pull request #2672 from 9rnsr/fix10684

[REG2.063][enh] Issue 10684 - Refused array op with array literal