On 2/6/14, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> Thanks. I guess we'd need to cross-reference to function names from there.

Updated to include function names.

On 2/6/14, 10:05 AM, grm wrote:
> On Thursday, 6 February 2014 at 17:57:45 UTC, Andrei Alexandrescu wrote:
>> On 2/6/14, 9:21 AM, Andrej Mitrovic wrote:
>>> On 2/6/14, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
>>>> On 2/6/14, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
>>>>> https://raw.github.com/AndrejMitrovic/phobos_allocations/master/phobos_allocations.txt
>>>>>
>>>>
>>>> Ah just realized there are duplicates in the report. I guess -vgc is
>>>> emitting dupes.
>>>
>>> Updated to remove duplicate reports.
>>
>> Thanks. I guess we'd need to cross-reference to function names from
>> there.
>>
>> Andrei
>
> and also new *XY*Exception doesn't indicate a problem necessarily

Good point. Seems to me code inspection would be a simpler way.

Andrei

On 2/6/14, 10:05 AM, Johannes Pfau wrote:
> Am Thu, 06 Feb 2014 16:32:08 +0000
> schrieb "Dicebot" <public@dicebot.lv>:
>
>> On Thursday, 6 February 2014 at 16:28:25 UTC, Andrei Alexandrescu
>> wrote:
>>> Would anyone be willing to take on the ingrate task of creating
>>> a comprehensive list with all Phobos functions (and more
>>> generally artifacts) that allocate memory? That would help a
>>> lot with focusing the discussion.
>>>
>>> Andrei
>>
>> Merging https://github.com/D-Programming-Language/dmd/pull/1886
>> and running phobos unit tests should make it relatively simple,
>> at least for a first pass.
>
> That's only for implicit allocations though. And please, don't merge
> yet, it'll get another rewrite this weekend ;-)

Please close if you plan to rewrite.

> One interesting point is that module that were written with avoiding
> allocations in mind usually still allocate when throwing exceptions.

Good point, we need to address that as well.


Andrei

On 2/6/14, 10:15 AM, Andrej Mitrovic wrote:
> On 2/6/14, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
>> Thanks. I guess we'd need to cross-reference to function names from there.
>
> Updated to include function names.

Noice. One

less phobos_allocations.txt | grep 'In function'| sed "s/.*'\\(.*\\)':/\\1/"|sort|uniq >phobos_allocating_functions.txt

later, and...


Andrei

On Thursday, 6 February 2014 at 18:25:34 UTC, Andrei Alexandrescu wrote:
> Noice. One
>
> less phobos_allocations.txt | grep 'In function'| sed
> "s/.*'\\(.*\\)':/\\1/"|sort|uniq
> >phobos_allocating_functions.txt
>
> later, and...

Well I'm just hacking on the -vgc pull to output what I want, but I should read titles better :). Here's the functions:

http://codepad.org/3TsPXryX

On 2/6/14, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> Noice. One
>
> less phobos_allocations.txt | grep 'In function'| sed "s/.*'\\(.*\\)':/\\1/"|sort|uniq >phobos_allocating_functions.txt
>
> later, and...

Ah you've attached a file, didn't notice it on the left since I
usually skim the avatar part:
http://forum.dlang.org/thread/ld0d79$2ife$1@digitalmars.com?page=2#post-ld0k2u:242ptu:241:40digitalmars.com

>> That's only for implicit allocations though. And please, don't merge
>> yet, it'll get another rewrite this weekend ;-)
>
> Please close if you plan to rewrite.
>
>
>
> Andrei


expecting the requested close, so some OTs (in random order):

- bought TDPL shortly after it's been released
- was very impressed by the concept
- following the NGs since, I guess, 2010
- great community and *very* smart people
- had nothing of value to add yet, tough (since I'm stuck with C/C++/Jave and some proprietary stuff)

- and today I submitted my first reply, which was incredibly easy.
  no annoyance!
  please make this more obvious for guys like me that do not want to register.

thx and good luck to you all
hope I can contribute my share some day

Kind Regards

On Thursday, 6 February 2014 at 18:20:56 UTC, Andrei Alexandrescu wrote:
>> One interesting point is that module that were written with avoiding
>> allocations in mind usually still allocate when throwing exceptions.
>
> Good point, we need to address that as well.
>
>
> Andrei

Hey, wait a second. How do you throw without allocating?

On 2/6/14, 10:52 AM, fra wrote:
> On Thursday, 6 February 2014 at 18:20:56 UTC, Andrei Alexandrescu wrote:
>>> One interesting point is that module that were written with avoiding
>>> allocations in mind usually still allocate when throwing exceptions.
>>
>> Good point, we need to address that as well.
>>
>>
>> Andrei
>
> Hey, wait a second. How do you throw without allocating?

I don't know yet. That's what the "addressing the problem" will take care of! :o)

Andrei

Am Thu, 06 Feb 2014 18:52:20 +0000
schrieb "fra" <a@b.it>:

> On Thursday, 6 February 2014 at 18:20:56 UTC, Andrei Alexandrescu wrote:
> >> One interesting point is that module that were written with
> >> avoiding
> >> allocations in mind usually still allocate when throwing
> >> exceptions.
> >
> > Good point, we need to address that as well.
> >
> >
> > Andrei
> 
> Hey, wait a second. How do you throw without allocating?
> 

You can store the exception as a global and that's done for the OutOfMemoryError IIRC, but what I meant was 'allocate with the GC'.