On Saturday, 27 June 2020 at 14:49:34 UTC, James Gray wrote:
I have produced something which essentially reproduces my
problem.
What is the problem? Do you have a leak or you want to know how
GC works?
On 6/29/20 4:34 PM, aberba wrote:
> So with this, without the Thread.sleep() to block main from exiting, the
> spawned thread will terminate immediately.
You can call core.thread.thread_joinAll at the end of main.
Another way would be to wait for a worker's exit by looking for
LinkTerminated
On Sunday, 28 June 2020 at 14:23:01 UTC, Stanislav Blinov wrote:
On Sunday, 28 June 2020 at 13:29:08 UTC, aberba wrote:
[...]
The error you're getting is because you're passing a pointer to
a delegate instead of a delegate.
[...]
So with this, without the Thread.sleep() to block
On Monday, 29 June 2020 at 22:31:12 UTC, Arjan wrote:
So when no inner scope is present, the scope exit 'runs' after
the return? Is that indeed expected behavior according to the
specification?
Yes. A scope ends at the '}'. Destructors and scope guards
execute then, after the return.
On 6/29/20 6:31 PM, Arjan wrote:
```
void main()
{
import std.stdio;
auto f = (){
string[] t;
{ // inner scope
t ~= "hello";
scope( exit ) t ~= "world";
} // inner scope exit
return t;
};
f().writeln; // ["hello", "world"]
}
```
removing the inner sc
```
void main()
{
import std.stdio;
auto f = (){
string[] t;
{ // inner scope
t ~= "hello";
scope( exit ) t ~= "world";
} // inner scope exit
return t;
};
f().writeln; // ["hello", "world"]
}
```
removing the inner scope in f() gives ["hello"]
So when no inner
On 6/29/20 1:50 PM, Jacob Carlborg wrote:
On Monday, 29 June 2020 at 16:34:33 UTC, Steven Schveighoffer wrote:
Are you sure? On the ABI page [1] , it says "The extern (C) and extern
(D) calling convention matches the C calling convention used by the
supported C compiler on the host system."
On Monday, 29 June 2020 at 16:34:33 UTC, Steven Schveighoffer
wrote:
Are you sure? On the ABI page [1] , it says "The extern (C) and
extern (D) calling convention matches the C calling convention
used by the supported C compiler on the host system."
In that case the documentation is wrong. H
On 6/26/20 4:15 AM, Jacob Carlborg wrote:
On Friday, 26 June 2020 at 00:30:22 UTC, Denis wrote:
I have a two questions about calling C functions from D.
(1) When passing a D callback to a C function, is there a way to write
the code without having to prefix the callback declaration with
"exte
On Sunday, 28 June 2020 at 07:09:53 UTC, Виталий Фадеев wrote:
I want light-weight runtime !
How to ?
Runtime provides language features that rely on extra code.
Removing that code from runtime means to give up on corresponding
language features. This way you can implement only features you
On Monday, 29 June 2020 at 12:25:16 UTC, Steven Schveighoffer
wrote:
On 6/29/20 5:14 AM, ichneumwn wrote:
[...]
Not in the standard library. Such things require an event
framework, because there is no OS-agnostic provided mechanism
to sleep on all these things at once.
I recommend looking
On 6/29/20 5:14 AM, ichneumwn wrote:
Dear all,
Is there some facility in D for a single statement/function call that
will wait on both file descriptors, like Socket.select(), and will also
wake up when there is something to be receive()'d?
Not in the standard library. Such things require an
On Monday, 29 June 2020 at 06:21:43 UTC, ag0aep6g wrote:
Since `local` and `writeln` are templates, the attributes for
their parameters are inferred from their bodies. `local!(int*)`
doesn't do anything with the parameter, so it's inferred as
`scope`. `writeln!(int*)` apparently does something
On Monday, 29 June 2020 at 06:29:38 UTC, Anthony wrote:
What does "__initZ" refer to?
Does this refer to automatic initialization like "this()"?
Almost, it's the static initializer for that struct, which is
omitted because you apparently don't compile/link the module
containing the struct dec
Dear all,
Is there some facility in D for a single statement/function call
that will wait on both file descriptors, like Socket.select(),
and will also wake up when there is something to be receive()'d?
One solution would be to have my main thread use receive() and a
helper thread that does
15 matches
Mail list logo
