Generally, I find sticking with the existing 1-based design most appealing. Making changes to conceptually trivial things such as this that require careful revision of existing code just to try to stay on the "right side of history" is likely to generate endless churn for no gain, as passing fashions keep on switching which is the "right side".
> Q: If we were designing Chapel from scratch, or you were approaching > it for the first time today, would you be happiest if its indexing was > 1-based or 0-based? > > 1 = I'd be happiest if it were 1-based > ... > 4 = It wouldn't really matter to me > ... > 7 = I'd be happiest if it were 0-based > 6 > > Q: Given that Chapel is not brand new, how enthusiastic is your > support for making it 1-based or 0-based today? > > 1 = I feel strongly that it should remain 1-based > ... > 4 = It wouldn't really matter to me > ... > 7 = I feel strongly that it should change to 0-based > 2 > > Q: How much do you worry about the impact such a change would have on > Chapel code that you've already written? > > 1 = Very worried: I expect the impact to be significant and would > not be enthusiastic about updating my code. > ... > 4 = Eh... I don't think this would be a big deal > ... > 7 = Not at all worried: I expect the impact to my code to be > minimal and/or I support the proposal strongly enough that I think > any pain would be worth it. > 3 > > Q: If we were to make the change and you are worried about it, would > it be possible/helpful if we were to help update your code? > > 1 = No, not possible: I'm not permitted to share my code with you > ... > 4 = It'd be possible, but I don't think I'd need the help, thanks > ... > 7 = It'd be possible and very helpful, thanks! 3 _______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
