Dealing with Autodecode

[Seb via Digitalmars-d]

On Wednesday, 1 June 2016 at 11:42:06 UTC, Seb wrote:
> On Wednesday, 1 June 2016 at 02:39:55 UTC, Nick Sabalausky 
> wrote:
>> On 05/31/2016 09:36 PM, Adam D. Ruppe wrote:
>>>
>>> version(string_migration)
>>> deprecated void popFront(T)(ref T t) if(isSomeString!T) {
>>>    static assert(0, "this is crap, fix your code.");
>>> }
>>> else
>>> deprecated("use -versionstring_migration to fix your buggy 
>>> code, would
>>> you like to know more?")
>>> /* existing popFront here */
>>>
>>
>> I vote we use Adam's exact verbiage, too! :)
>>
>>>
>>> D USERS **WANT** BREAKING CHANGES THAT INCREASE OVERALL CODE 
>>> QUALITY
>>> WITH A SIMPLE MIGRATION PATH!!!!!!!!!!!!!!!!!!!!
>>>
>>
>> Yes. This. If I wanted an endless bucket of baggage, I'd have 
>> stuck with C++.
>>
>>> 3) A wee bit longer, we exterminate all this autodecoding 
>>> crap and enjoy
>>> Phobos being a smaller, more efficient library.
>>>
>>
>> Yay! Profit!
>
>
> How about a poll?
>
> http://www.polljunkie.com/poll/ftmibx/remove-auto-decoding-in-d
>
> Results are shown after casting a vote or here:
> http://www.polljunkie.com/poll/aqzbwg/remove-auto-decoding-in-d/view

Just FYI after a short period of ten hours we got the following 
45 responses:

Yes, with fire! (hobby user)                                      
     77% (35)
Yeah remove that special behavior (professional user)             
     35% (16)
Wait that is what auto decoding is? wah ugh...                    
     8%  (4)
I don't always decode codeunits, but when I do I use byDChar 
already  6%  (3)