On Friday, 30 October 2015 at 05:21:17 UTC, Rikki Cattermole
wrote:
What I normally do for memory to be owned by the thread is:
auto foo(IAllocator alloc=theAllocator()) {...}
Where as for if it is global to the process:
auto foo(IAllocator alloc=processAllocator()) {...}
Basically it is the
On Sunday, 1 November 2015 at 09:48:20 UTC, ref2401 wrote:
On Friday, 30 October 2015 at 05:21:17 UTC, Rikki Cattermole
wrote:
What I normally do for memory to be owned by the thread is:
auto foo(IAllocator alloc=theAllocator()) {...}
Where as for if it is global to the process:
auto
On Friday, 30 October 2015 at 01:26:17 UTC, Rikki Cattermole
wrote:
Take a look at the functions theAllocator and processAllocator.
It would be greate if compiler were able to use `theAllocator`
and `processAllocator` but they don't seem much helpfull.
Terrible naming by the way.
On Friday, 30 October 2015 at 04:11:05 UTC, ref2401 wrote:
It would be greate if compiler were able to use `theAllocator`
and `processAllocator` but they don't seem much helpfull.
Terrible naming by the way.
I should have suggested different names if don't like present
ones.
if
On 30/10/15 5:27 PM, ref2401 wrote:
On Friday, 30 October 2015 at 04:11:05 UTC, ref2401 wrote:
It would be greate if compiler were able to use `theAllocator` and
`processAllocator` but they don't seem much helpfull. Terrible naming
by the way.
I should have suggested different names if don't
On 30/10/15 7:56 AM, ref2401 wrote:
As I understand the `std.experimental.allocator` package will be
included in the upcoming DMD 2.069 release. I like the idea of
composable allocators. Though I've got a question which I can not answer
myself.
Let's assume a team which is developing an
