Bug 4197 – ICE(glue.c): error in forward-referenced in/out contract
Status
RESOLVED
Resolution
FIXED
Severity
major
Priority
P2
Component
dmd
Product
D
Version
D2
Platform
Other
OS
All
Creation time
2010-05-16T04:20:00Z
Last change time
2015-06-09T05:11:44Z
Keywords
ice-on-invalid-code
Assigned to
nobody
Creator
strtr
Comments
Comment #0 by strtr — 2010-05-16T04:20:19Z
module main;
const S S1 = S();
struct S
{
static S func( S s_ )
in{ assert(false,random); }
out(result){ assert(false,random); }
body{ return s_; }
const S S2 = func(S());
}
void main(){}
--
main.d(8): Error: __error <---# should be assert failure #
main.d(12): Error: cannot evaluate func((S())) at compile time
Comment #1 by Justin.SpahrSummers — 2010-05-16T10:48:17Z
(In reply to comment #0)
> module main;
>
> const S S1 = S();
>
> struct S
> {
> static S func( S s_ )
> in{ assert(false,random); }
> out(result){ assert(false,random); }
> body{ return s_; }
>
> const S S2 = func(S());
> }
> void main(){}
> --
> main.d(8): Error: __error <---# should be assert failure #
> main.d(12): Error: cannot evaluate func((S())) at compile time
The second argument to assert() - if present - is supposed to be a string describing the condition. The error message without the second parameter or with a string there instead is correct.
Comment #2 by bearophile_hugs — 2010-05-16T11:03:13Z
This can be a simplified version of the same problem:
enum Foo F1 = Foo();
struct Foo {
const Foo F2 = func();
}
Foo func() {
assert(false, random);
return Foo();
}
void main() {}
Comment #3 by strtr — 2010-05-16T14:11:22Z
(In reply to comment #1)
>
> The second argument to assert() - if present - is supposed to be a string
> describing the condition. The error message without the second parameter or
> with a string there instead is correct.
I was expecting something like :
Error: cannot implicitly cast "random" of type unknown to string
Or
Error: "random" not defined
Comment #4 by clugdbug — 2011-04-28T13:12:33Z
Original title was:
"__error iso assert failure in struct function in/out statement"
A reduced test case shows it is a very general ICE.
*Any* error inside an in() or out() contract in a function that is has its semantic run through CTFE, has all errors gagged. This can result in a cryptic error message (as in the original test case), or an ICE. This one is ICE(glue.c), but I've also seen ICE(toir.c). It fails on both D1 and D2.
const Bug4197 s4197 = Bug4197();
int func4197()
in { undefined; }
body { return 0; }
struct Bug4197 {
static const int S2 = func4197();
}