[Bug libstdc++/9679] Strange behaviour of valarray::apply method

["gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From gdr at integrable-solutions dot net  2004-03-19 19:12 -------
Subject: Re:  Strange behaviour of valarray::apply method

"pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org> writes:

| However, what I'm missing is why "won't fix" or, even more weird to
| me, "suspend" Usually "suspend" is used when waiting for something
| to happen. What, in this case? Not the resolution of a DR, right?
| 
| And also "won't fix": it would imply that actually we acknowledge
| the library is buggy wrt the standard but for some reason we don't
| want to fix. Is really like that?
| 
| Isn't simply "not a bug"???


It is clearly "Not a bug" with current C++ (either 98 or 2003 would do).


With the DR I submitted, and that would be accepted as part of C++0x,
it would become a bug in the lirbary ; but it would be a bug only
because I did not anticipate that part when making the new proposed
wording.  Let me be clear:  Before my proposal, the PR is invalid
because the code is ill-formed.  With my proposal as currently worded,
the code would become valid (but I did not intend it to be valid).

The reason I did not intend it to be valid is that if it were valid it
would rule out possibility to use expression templates to implement
<valarray> and that would result in huge performance loss.

I said "won't fix" because, the program was invalid and should stay
invalid, but I didn't have wording for that right now.  That is a very
optimistic anticipation.  The pessimistic anticipation is to wait and
see.   Which means "suspend".

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9679