Blog post on making Voldemort types without the disk-space issues: http://www.schveiguy.com/blog/2016/05/have-your-voldemort-types-and-keep-your-disk-space-too/

-Steve

On Tuesday, 24 May 2016 at 01:29:53 UTC, Steven Schveighoffer wrote:
> Blog post on making Voldemort types without the disk-space issues: http://www.schveiguy.com/blog/2016/05/have-your-voldemort-types-and-keep-your-disk-space-too/

Good illustration and reasonable solution.

"I will be splitting my functions Horcrux style". :)

On Tuesday, 24 May 2016 at 01:29:53 UTC, Steven Schveighoffer wrote:
> Blog post on making Voldemort types without the disk-space issues: http://www.schveiguy.com/blog/2016/05/have-your-voldemort-types-and-keep-your-disk-space-too/
>
> -Steve

Very useful - thanks!

On Tuesday, 24 May 2016 at 01:29:53 UTC, Steven Schveighoffer wrote:
> Blog post on making Voldemort types without the disk-space issues: http://www.schveiguy.com/blog/2016/05/have-your-voldemort-types-and-keep-your-disk-space-too/
>
> -Steve

Should we horcruxify Phobos?

Atila

On Tuesday, 24 May 2016 at 01:29:53 UTC, Steven Schveighoffer wrote:
> http://www.schveiguy.com/blog/2016/05/have-your-voldemort-types-and-keep-your-disk-space-too/

Good read. I'll horcruxify my phobos-next ranges until compiler is fixed. Thanks!

On 5/25/16 4:22 AM, Atila Neves wrote:
> On Tuesday, 24 May 2016 at 01:29:53 UTC, Steven Schveighoffer wrote:
>> Blog post on making Voldemort types without the disk-space issues:
>> http://www.schveiguy.com/blog/2016/05/have-your-voldemort-types-and-keep-your-disk-space-too/
>>
>
> Should we horcruxify Phobos?

As far as low-hanging fruit, I think it may be worthwhile, since this is really an implementation detail. The fixing of true Voldemort types is likely not happening for a few releases, as the principles don't seem to agree on the best mechanism.

-Steve

On Wednesday, 25 May 2016 at 12:19:33 UTC, Steven Schveighoffer wrote:
> On 5/25/16 4:22 AM, Atila Neves wrote:
>> On Tuesday, 24 May 2016 at 01:29:53 UTC, Steven Schveighoffer wrote:
>>> Blog post on making Voldemort types without the disk-space issues:
>>> http://www.schveiguy.com/blog/2016/05/have-your-voldemort-types-and-keep-your-disk-space-too/
>>>
>>
>> Should we horcruxify Phobos?
>
> As far as low-hanging fruit, I think it may be worthwhile, since this is really an implementation detail. The fixing of true Voldemort types is likely not happening for a few releases, as the principles don't seem to agree on the best mechanism.
>
> -Steve

I also agree that fixing phobos this way is a good low hanging fruit. Having symbol name and binary size explosion when using basic phobos functionality could act as deterrent for early adoption of the D language.