Bug 6912 – const(T)[] can be implicitly cast to inout(const(T)[])
Status
RESOLVED
Resolution
FIXED
Severity
critical
Priority
P2
Component
dmd
Product
D
Version
D2
Platform
All
OS
All
Creation time
2011-11-08T16:03:00Z
Last change time
2011-11-14T21:11:55Z
Keywords
accepts-invalid, patch
Assigned to
nobody
Creator
timon.gehr
Comments
Comment #0 by timon.gehr — 2011-11-08T16:03:34Z
Consider:
int[] y;
inout(const(int)[]) foo(inout(int) x){
y=new int[10];
const(int)[] q = y;
inout a = q;
return a;
}
void main(){
immutable int x;
immutable int[] oops = foo(x);
assert(is(typeof(oops[0]) == immutable));
auto oldoops_0 = oops[0];
y[0]++;
assert(oops[0] != oldoops_0);
}
This is caused by the fact that !is(inout(const(int)[])==inout(int[])), i.e. inout is currently non-transitive in certain cases and making it 'override' const transitively will fix the issue.
Comment #1 by schveiguy — 2011-11-09T06:35:05Z
inout a = q;
This line should fail to compile. const does not implicitly cast to inout.
Note that:
immutable a = q;
doesn't work. inout should follow the same restrictions.
I don't think this has to do with transitivity (and indeed, inout cannot override const or immutable). It's just a simple case of inout cannot be implicitly cast from something else.
Remember, inout can get implicitly cast back to immutable or mutable upon function return. I don't think inout should override *any* qualifiers without casts.
Comment #2 by timon.gehr — 2011-11-09T08:58:10Z
(In reply to comment #1)
> inout a = q;
>
> This line should fail to compile. const does not implicitly cast to inout.
>
Yes, but the issue here is that it casts to inout(const(int)[]). (dmd rejects casting const(int[]) to inout(int[]) for exampe)
> Note that:
>
> immutable a = q;
>
> doesn't work. inout should follow the same restrictions.
>
> I don't think this has to do with transitivity (and indeed, inout cannot
> override const or immutable). It's just a simple case of inout cannot be
> implicitly cast from something else.
>
> Remember, inout can get implicitly cast back to immutable or mutable upon
> function return. I don't think inout should override *any* qualifiers without
> casts.
You are right, it is not a transitivity/overriding issue.
Currently inout(const(T)) == inout(immutable(T)) == inout(T). That is bad, for example, how to represent the element type of inout(const(char)[]) ? (DMD treats it as const(char), which is obviously wrong, it should be inout(const(char)).)
I think this should be accepts-invalid, since the given example code should not compile.
Comment #5 by k.hara.pg — 2011-11-10T06:07:48Z
(In reply to comment #4)
> I think this should be accepts-invalid, since the given example code should not
> compile.
Wow, I'm sorry, and thank you for your fix.
Comment #6 by schveiguy — 2011-11-10T06:49:38Z
(In reply to comment #5)
> (In reply to comment #4)
> > I think this should be accepts-invalid, since the given example code should not
> > compile.
>
> Wow, I'm sorry, and thank you for your fix.
Don't worry about it! The main fix is the patch, my change was a nitpick :)