On Saturday, 24 March 2018 at 20:31:48 UTC, H. S. Teoh wrote:
On Sat, Mar 24, 2018 at 04:59:49PM +, Russel Winder via
Digitalmars-d wrote:
On Sat, 2018-03-24 at 09:45 -0700, H. S. Teoh via
Digitalmars-d wrote:
> […]
>
> That is why a sane build system should always cache
> dependencies lo
On Sunday, 8 April 2018 at 13:00:02 UTC, bauss wrote:
I think it's better demonstrated like this, because to me the
behavior makes no sense.
Especially since you can just cast "Bar" to "Foo" and then
you're allowed to do it.
Since we're inside Foo then it shouldn't care whether "_baz" is
pr
On Monday, 9 April 2018 at 17:16:56 UTC, bauss wrote:
On Monday, 9 April 2018 at 17:05:45 UTC, martin wrote:>>
Actually, this behaves as i would expect.
`_baz` is a private member of Foo (to be precise: it belongs
to module `a`)
in handleBar(), you iterate `Bar[]` - which is in module `b`.
By
Are there any C-like bitfields in D?
Yes - How can I use them?
No - What could be used in their stead?
On Friday, 30 December 2016 at 14:06:06 UTC, Marc Schütz wrote:
On Friday, 30 December 2016 at 13:45:23 UTC, Martin wrote:
Are there any C-like bitfields in D?
Yes - How can I use them?
No - What could be used in their stead?
Not built-in, but in the standard library:
https://dlang.org/phobo
The cost of using the current GC in D, although beneficial for
many types of programs, is unaffordable for programs such as
games, etc... that need to perform repetitive tasks every short
periods of time. The fact that a GC.malloc/realloc on any thread
can trigger a memory collection that stop
On Tuesday, 23 September 2014 at 01:58:50 UTC, Rikki Cattermole
wrote:
Short, I dislike pretty much all changes to __gshared/shared.
Breaks too many things.
Atleast with Cmsed, (I'm evil here) where I use __gshared
essentially as a read only variable but modifiable when
starting up (to modify n
On Tuesday, 23 September 2014 at 15:28:30 UTC, Marc Schütz wrote:
On Tuesday, 23 September 2014 at 15:23:16 UTC, Kagamin wrote:
And what GC does? Pins the allocated blocks for another thread?
Assuming there is one thread-local GC per thread, it transfers
responsibility of the allocated data f
On Tuesday, 23 September 2014 at 16:47:09 UTC, David Nadlinger
wrote:
On Tuesday, 23 September 2014 at 10:38:29 UTC, Kagamin wrote:
The question is how thread-local GC will account for data
passed to another thread.
I was briefly discussing this with Andrei at (I think) DConf
2013. I suggeste
On Wednesday, 24 September 2014 at 08:13:15 UTC, Marc Schütz
wrote:
On Tuesday, 23 September 2014 at 18:39:09 UTC, Oscar Martin
wrote:
On Tuesday, 23 September 2014 at 01:58:50 UTC, Rikki
Cattermole wrote:
Short, I dislike pretty much all changes to __gshared/shared.
Breaks too many things.
Atl
On Wednesday, 24 September 2014 at 11:59:52 UTC, Kagamin wrote:
On Tuesday, 23 September 2014 at 16:47:09 UTC, David Nadlinger
wrote:
I was briefly discussing this with Andrei at (I think) DConf
2013. I suggested moving data to a separate global GC heap on
casting stuff to shared.
Yes, that s
On Thursday, 25 September 2014 at 13:55:42 UTC, Wyatt wrote:
On Wednesday, 24 September 2014 at 20:15:52 UTC, Oscar Martin
wrote:
On Wednesday, 24 September 2014 at 08:13:15 UTC, Marc Schütz
wrote:
There can also be a shared _and_ a local GC at the same time,
and a thread could opt from the s
12 matches
Mail list logo
