immutable bug?

[Timon Gehr]

On 01/12/2014 11:51 PM, Andrei Alexandrescu wrote:
> ...
>>>
>>> Put $150 on this.
>>> https://www.bountysource.com/issues/1325974-type-system-breaking-caused-by-implicit-conversion-for-the-value-returned-from-pure-function
>>>
>>>
>>>
>>>
>>> Andrei
>>
>> This issue was trivial, and yet was assigned a higher bounty than e.g.
>> fixing CTFE performance, which requires a large investment as far as I
>> understand. This raises the question of how bountied issues are
>> selected.
>
> I select them with a focus on impact. Clearly the process could be
> improved.
> ...

I see. FWIW it _did_ get an issue fixed.

>   There are other serious problems with the type system
>> implementation, eg:
>>
>> https://d.puremagic.com/issues/show_bug.cgi?id=9149
>> https://d.puremagic.com/issues/show_bug.cgi?id=10376
>> https://d.puremagic.com/issues/show_bug.cgi?id=9148
>
> Thanks, will take those under advisement.  FWIW there's been a thread
> taking suggestions.
> ...

(I know; at that time I didn't think those issues would qualify. :o))

>> On a related note, I think it makes no sense to put a bounty on the
>> "Object not const-correct" issue. What would someone be required to do
>> in order to get the bounty for that issue?
>
> Make sure we have a complete solution for invoking Object's methods
> against const and immutable Objects?
>
>
> Andrei
>

Wasn't there a consensus that Object's methods are going away?