Hi Chapel Developers --
A bug I ran into today made me realize the following for the first time:
Back in the dark ages when we didn't have array literals, we used tuple
literals as the means of initializing arrays, primarily because we had no
other recourse. Thus, you'd write:
var A: [1..3] real = (1.2, 3.4, 5.6);
Now that we're in the middle ages, a savvy Chapel programmer would write
this as:
var A: [1..3] real = [1.2, 3.4, 5.6];
or even:
var A = [1.2, 3.4, 5.6];
But somehow it had escaped my attention that we never disabled the "assign
tuple to array" case. I'm thinking that we probably should, but wanted to
see if there were any opposing viewpoints.
Simultaneously with expressing this opinion, I'm checking to see whether
there are any cases in the test suite that suggest preserving the
capability, or whether they should just be rewritten to use array
literals. All the ones I've seen so far are the latter cases.
Thanks,
-Brad
PS -- Sadly, this realization didn't actually help with my bug...
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
Chapel-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-developers
