Bug 2177 – dstress nocompile section get something should be in compile section?

Status
RESOLVED
Resolution
INVALID
Severity
normal
Priority
P2
Component
tools
Product
D
Version
D1 (retired)
Platform
x86
OS
Windows
Creation time
2008-06-26T00:10:00Z
Last change time
2015-06-09T01:36:17Z
Assigned to
thomas-dloop
Creator
davidl

Comments

Comment #0 by davidl — 2008-06-26T00:10:47Z
nocompile has two different meanings, 1. the code shouldn't be compiled. 2. the code should be compilable but it *was* rejected by the compiler maybe condition 2 should be moved to compile section? like following: kuehne\nocompile\b\bug_cgcs_354_A.d kuehne\nocompile\b\bug_cgcs_354_B.d kuehne\nocompile\b\bug_cod1_1656_B.d kuehne\nocompile\b\bug_cod1_1656_H.d kuehne\nocompile\b\bug_tocsym_142_A.d kuehne\nocompile\b\bug_tocsym_142_B.d kuehne\nocompile\b\bug_tocsym_142_C.d kuehne\nocompile\b\bug_tocsym_142_D.d kuehne\nocompile\b\bug_tocsym_142_E.d kuehne\nocompile\b\bug_toir_170_A.d kuehne\nocompile\b\bug_toir_170_B.d kuehne\nocompile\b\bug_type_308_G.d kuehne\nocompile\b\bug_type_308_H.d
Comment #1 by kamm-removethis — 2008-09-09T10:48:24Z
No, I believe most of these contain real nocompile test cases: > kuehne\nocompile\b\bug_cgcs_354_A.d > kuehne\nocompile\b\bug_cgcs_354_B.d Borderline case. casts really aren't specified well enough. > kuehne\nocompile\b\bug_cod1_1656_B.d > kuehne\nocompile\b\bug_cod1_1656_H.d Not sure, I have a feeling the short-circuiting shouldn't circumvent checking the semantics... > kuehne\nocompile\b\bug_tocsym_142_A.d > kuehne\nocompile\b\bug_tocsym_142_B.d > kuehne\nocompile\b\bug_tocsym_142_C.d > kuehne\nocompile\b\bug_tocsym_142_D.d Static function can't access this.member. > kuehne\nocompile\b\bug_tocsym_142_E.d S is not an instance. > kuehne\nocompile\b\bug_toir_170_A.d > kuehne\nocompile\b\bug_toir_170_B.d Static function can't create nested class. > kuehne\nocompile\b\bug_type_308_G.d > kuehne\nocompile\b\bug_type_308_H.d foo is not a static function.