Re: Process in parallel and output result to stdout theread-safely

2018-09-11 Thread Dr.No via Digitalmars-d-learn
On Monday, 10 September 2018 at 20:30:52 UTC, Dr.No wrote: On Saturday, 8 September 2018 at 14:26:45 UTC, ag0aep6g wrote: [...] Yes, it does only happens at line breaks. I hadn't realized that until you mentioned. It does gets in place of \r and \n, that's why there's all in one line when

Re: How to use listener.d example?

2018-09-11 Thread Marcin via Digitalmars-d-learn
On Friday, 7 September 2018 at 17:00:21 UTC, Marcin wrote: I get it working in linux environment. I don't know why vibe-d get linker errors on win10. And I get it to work on windos dub --build=release

enforce with return type RegexMatch!string

2018-09-11 Thread berni via Digitalmars-d-learn
I've got the folling function which returns a RegexMatch!string: auto extract_list(const string entry) { // check if entry is valid return matchAll(entry, some_regex); } I call this function using enforce(extract_list(some_argument)). I think, that enforce is quite useless in this

Re: Is it's correct to say that ALL types that can grow are place on heap?

2018-09-11 Thread drug via Digitalmars-d-learn
11.09.2018 13:11, Timoses пишет: Is this why it is said that passing parameters by value can be more efficient? Cause for a ref parameter it would require passing the address which would require to be allocated? Aww, I really would love some insights into function parameter passing. Why is

Re: "immutable string" vs "const string*"

2018-09-11 Thread Timoses via Digitalmars-d-learn
On Sunday, 9 September 2018 at 08:41:37 UTC, Christian Mayer wrote: On Sunday, 9 September 2018 at 08:14:41 UTC, rikki cattermole wrote: Are you aware that a string is just an alias of immutable(char)[]? Yes, I'm aware of that. But it's the same, for example, with just one char. "immutable

Re: Is it's correct to say that ALL types that can grow are place on heap?

2018-09-11 Thread Timoses via Digitalmars-d-learn
On Saturday, 8 September 2018 at 22:51:17 UTC, Ali Çehreli wrote: On 09/08/2018 02:19 AM, Suliman wrote: > Is it's correct to say that ALL types that can grow are place on heap > and types that not growing (int, char, pointer) are place on stack? The question is not that simple. :) First,

Re: traits getOverload of a template method

2018-09-11 Thread Basile B. via Digitalmars-d-learn
On Thursday, 6 February 2014 at 23:06:03 UTC, QAston wrote: How do i get aliases to overloads of a template method like Class A { int a(T)(T tq,T tw); int a(T)(T tq); } __traits(getOverloads, A, "a(int)")doesnt work Support for template in the getOverloads trait has been added