Bug 7937 – Range iota.Result should be const where possible
Status
RESOLVED
Resolution
FIXED
Severity
enhancement
Priority
P2
Component
phobos
Product
D
Version
D2
Platform
All
OS
All
Creation time
2012-04-18T11:33:00Z
Last change time
2015-06-09T05:14:44Z
Assigned to
nobody
Creator
andre.stein.1985
Comments
Comment #0 by andre.stein.1985 — 2012-04-18T11:33:52Z
The operators opSlice and opIndex of iota.Result should be const as they don't mutate the range. This allows passing the range as const to functions which only use those two operators.
Comment #1 by lovelydear — 2012-04-19T05:52:28Z
Is there a mailing-list discussion about this one ?
Comment #2 by bearophile_hugs — 2012-04-19T15:23:41Z
(In reply to comment #1)
> Is there a mailing-list discussion about this one ?
The place for discussions about a small and very specific bug is in Bugzilla threads.
Larger general enhancement requests are probably better discussed first in the newsgroup.
This enhancement request is small and very focused, so I think discussing it here is enough (but advertising it the newsgroup too is good).
Comment #3 by lovelydear — 2012-04-19T15:47:50Z
The problem is, if noone is interested in discussing these in the forums, noone will be interested in fixing these as it requires some effort. So all they do is add a little bit of noise and die.
Comment #4 by bearophile_hugs — 2012-04-19T16:24:28Z
(In reply to comment #3)
> The problem is, if noone is interested in discussing these in the forums, noone
> will be interested in fixing these as it requires some effort.
Probably 70-80% of Bugzilla issues, if presented in the newsgroup, will produce no answers (or one-two answers top). Yet, many of them get fixed. Something similar happens for little enhancement requests.
Newsgroups are not the right place for most bugs discussions. Newsgroups are mostly for the ones that are controversial, or require large changes, or cause breaking changes, etc.