[Issue 17479] Public constructor for std.process.Pid

https://issues.dlang.org/show_bug.cgi?id=17479 Chris Wright changed: What|Removed |Added Priority|P1 |P3 --

[Issue 17479] New: Public constructor for std.process.Pid

https://issues.dlang.org/show_bug.cgi?id=17479 Issue ID: 17479 Summary: Public constructor for std.process.Pid Product: D Version: D2 Hardware: x86_64 OS: All Status: NEW Severity: enhancement

[Issue 17478] New: Socket.select return a write status change, but no connection is established.

https://issues.dlang.org/show_bug.cgi?id=17478 Issue ID: 17478 Summary: Socket.select return a write status change, but no connection is established. Product: D Version: D2 Hardware: x86_64 OS: Other

[Issue 15692] Allow struct member initializer everywhere

https://issues.dlang.org/show_bug.cgi?id=15692 greensunn...@gmail.com changed: What|Removed |Added CC||greensunn...@gmail.com --- Comment

[Issue 17477] DMD error message for delegate with wrong attributes is very confusing

https://issues.dlang.org/show_bug.cgi?id=17477 Eyal changed: What|Removed |Added Keywords||diagnostic --

[Issue 17477] New: DMD error message for delegate with wrong attributes is very confusing

https://issues.dlang.org/show_bug.cgi?id=17477 Issue ID: 17477 Summary: DMD error message for delegate with wrong attributes is very confusing Product: D Version: D2 Hardware: x86_64 OS: Linux

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 --- Comment #5 from Eyal --- (In reply to Vladimir Panteleev from comment #4) > Adding `ref` to `char a` fixes compilation, but it's still weird that > `ref`'s presence is inconsistently needed. It also changes the meaning of the

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 ag0ae...@gmail.com changed: What|Removed |Added Keywords||rejects-valid CC|

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #8 from Vladimir Panteleev --- (In reply to Mathias Lang from comment #7) > How can > "foobar" be printed twice if it's only set for one thread ? Because both times "foobar" is written are done from the same

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #7 from Mathias Lang --- When a thread runs I would expect the following (simplified) course of action: - Initialize the TLS data - Do the writeln - Exit Given the original code, I would then expect the

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #6 from Andrej Mitrovic --- > In main, you set the TLS instance of path corresponding to the main thread to > "foobar". The "parallel" loop body will use the current thread's TLS > instance, but because the

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #5 from Vladimir Panteleev --- (In reply to Mathias Lang from comment #4) > So you can implicitly capture TLS variables and use them from other thread ? > Doesn't that completely defeat the purpose of thread

[Issue 17469] View source code

https://issues.dlang.org/show_bug.cgi?id=17469 --- Comment #3 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/d02045747db953d021649f222e07c71c0705dbb0 Fix Issue 17469 - View source code for object.d is

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Mathias Lang changed: What|Removed |Added CC|

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Vladimir Panteleev changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 17475] [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 --- Comment #3 from Vladimir Panteleev --- (In reply to b2.temp from comment #2) > Are you sure ? Yes: ~/work/Digger/work/repo » git checkout 13da2d4e97bf15c7049138012bde243a221be117 ; git submodule update ; git submodule

[Issue 17475] [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 --- Comment #2 from b2.t...@gmx.com --- (In reply to Vladimir Panteleev from comment #1) > You have a mismatching libphobos again. > > In the future, please test with a D build tool that removes the possibility > of user errors, such as Digger. Are

[Issue 17475] [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 Vladimir Panteleev changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 16566] hasLength should enforce that length has type size_t

https://issues.dlang.org/show_bug.cgi?id=16566 --- Comment #5 from Andrei Alexandrescu --- (In reply to Vladimir Panteleev from comment #4) > What about e.g. ranges representing files over 4GB on 32-bit architectures? Those are not supported. --

[Issue 16566] hasLength should enforce that length has type size_t

https://issues.dlang.org/show_bug.cgi?id=16566 Vladimir Panteleev changed: What|Removed |Added CC|

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 --- Comment #4 from Vladimir Panteleev --- Adding `ref` to `char a` fixes compilation, but it's still weird that `ref`'s presence is inconsistently needed. --

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 --- Comment #3 from Vladimir Panteleev --- (In reply to Eyal from comment #2) > Perhaps you didn't pass -unittest? Yep, my bad --

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 --- Comment #2 from Eyal --- (In reply to Vladimir Panteleev from comment #1) > Your example works here. Could you specify the compiler version and > compilation flags? dmd --version DMD64 D Compiler v2.074.0 Copyright (c) 1999-2017

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 Vladimir Panteleev changed: What|Removed |Added CC|

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Stefan Koch changed: What|Removed |Added CC||uplink.co...@gmail.com

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #1 from anonymous4 --- In the first thread it will be "foobar", in other threads it will be "/some/string/initializer", the exact sequence may depend on how parallel selects threads. --

[Issue 17476] New: Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Issue ID: 17476 Summary: Static fields don't seem to be reliably initialized when using parallel() Product: D Version: D2 Hardware: x86_64 OS: Linux

[Issue 17475] New: [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 Issue ID: 17475 Summary: [REG2.075] linker error on specific code Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: regression

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 ZombineDev changed: What|Removed |Added CC|

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 Tomer Filiba (weka) changed: What|Removed |Added Keywords||industry

[Issue 9275] [GC] removeRoot hits assert(0) instead of being a no-op (as documented)

https://issues.dlang.org/show_bug.cgi?id=9275 --- Comment #4 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/a1fb3915f562428741324ac5b319d9316fb57231 Fix issue 9275: Add test for removeRoot Issue 9275

[Issue 9275] [GC] removeRoot hits assert(0) instead of being a no-op (as documented)

https://issues.dlang.org/show_bug.cgi?id=9275 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED