[Issue 9275] [GC] removeRoot hits assert(0) instead of being a no-op (as documented)
https://issues.dlang.org/show_bug.cgi?id=9275 safety0ff.bugz changed: What|Removed |Added Keywords||bootcamp CC||safety0ff.b...@gmail.com --- Comment #2 from safety0ff.bugz --- A unit test should be added and then this bug should be closed. --
[Issue 12625] implicit slicing of RValue static array should be illegal
https://issues.dlang.org/show_bug.cgi?id=12625 ZombineDev changed: What|Removed |Added Keywords||safe --
[Issue 9275] [GC] removeRoot hits assert(0) instead of being a no-op (as documented)
https://issues.dlang.org/show_bug.cgi?id=9275
Nemanja Boric <4bur...@gmail.com> changed:
What|Removed |Added
CC||4bur...@gmail.com
--- Comment #1 from Nemanja Boric <4bur...@gmail.com> ---
Looks like this has been fixed in the meantime:
```
import core.memory;
void main()
{
// this will work fine
GC.removeRoot(null);
//this will boom once liner search fails to find '13' among roots
//It does the same with any sane pointer that isn't a root
GC.removeRoot(cast(void*)13);
}
```
--
[Issue 1001] print stack trace (in debug mode) when program die
https://issues.dlang.org/show_bug.cgi?id=1001 Andrei Alexandrescu changed: What|Removed |Added Assignee|nob...@puremagic.com|alexandru.razva...@gmail.co ||m --
[Issue 1001] print stack trace (in debug mode) when program die
https://issues.dlang.org/show_bug.cgi?id=1001 Andrei Alexandrescu changed: What|Removed |Added Assignee|lucia.mcojoc...@gmail.com |nob...@puremagic.com --
[Issue 8829] std.algorithm.find fails to take advantage of SortedRange
https://issues.dlang.org/show_bug.cgi?id=8829 Andrei Alexandrescu changed: What|Removed |Added Assignee|nob...@puremagic.com|razvan.nitu1...@gmail.com --
[Issue 8087] Improve clarity of std.algorithm documentation
https://issues.dlang.org/show_bug.cgi?id=8087 Andrei Alexandrescu changed: What|Removed |Added Assignee|nob...@puremagic.com|alexandru.razva...@gmail.co ||m --
[Issue 8799] Give example of Tuple mapped to a function
https://issues.dlang.org/show_bug.cgi?id=8799 Andrei Alexandrescu changed: What|Removed |Added Assignee|nob...@puremagic.com|lucia.mcojoc...@gmail.com --
[Issue 16574] [REG 2.072.0-b1] Unexplained errors about functions that overridde anything
https://issues.dlang.org/show_bug.cgi?id=16574 --- Comment #12 from b2.t...@gmx.com --- By the way Mr Nowak, I like to see how you're involved. But for this particular regression, maybe Kenji Hara could get in... If at a certain point he's not able to fix the new compiler feature: https://dlang.org/changelog/2.072.0.html#deferred_alias Then let's revert this feature until he has the time to work on it. --
[Issue 16629] New: [Reg 2.072] scope is stripped from some parameters
https://issues.dlang.org/show_bug.cgi?id=16629
Issue ID: 16629
Summary: [Reg 2.072] scope is stripped from some parameters
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: regression
Priority: P1
Component: dmd
Assignee: nob...@puremagic.com
Reporter: c...@dawg.eu
cat > bug.d << CODE
import std.traits;
struct T
{
void method1(scope int* foo){}
void method2(scope int foo){}
}
static assert(ParameterStorageClassTuple!(T.method1)[0] ==
ParameterStorageClass.scope_);
static assert(ParameterStorageClassTuple!(T.method2)[0] ==
ParameterStorageClass.scope_);
CODE
dmd -c bug
bug.d(10): Error: static assert (0u == cast(ParameterStorageClass)1u) is false
The scope storage class is ignored for some parameters (value parameters) and
no longer present in the tuple returned by `is(typeof(func) PR ==
__parameters)`.
Should at least be part of the changelog.
https://github.com/dlang/dmd/pull/5897
--
[Issue 15482] new uuid.d forbids to link statically with other libraries
https://issues.dlang.org/show_bug.cgi?id=15482 --- Comment #6 from Manu --- Okay... so, extern to them and remove the definitions in druntime? --
[Issue 15482] new uuid.d forbids to link statically with other libraries
https://issues.dlang.org/show_bug.cgi?id=15482 --- Comment #5 from Martin Nowak --- (In reply to Manu from comment #4) It's probably just a mistake from adding the Windows headers. --
[Issue 5118] Stack traces should properly handle nested functions
https://issues.dlang.org/show_bug.cgi?id=5118 Nemanja Boric <4bur...@gmail.com> changed: What|Removed |Added Status|NEW |RESOLVED CC||4bur...@gmail.com Resolution|--- |FIXED --- Comment #2 from Nemanja Boric <4bur...@gmail.com> --- I think the problem here is that previous exception handler was using BPs stored on stack to walk the stack frame, and nested functions were not doing this properly (if I remember correctly, they were not using *BP for the stack frame, or something similar). With the new exception handler, this issue is gone: object.Exception@test.d(8): Test. ??:? void test.doIt().nested() [0x422ae9] ??:? void test.doIt() [0x422a92] ??:? _Dmain [0x422a80] ??:? _D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ6runAllMFZ9__lambda1MFZv [0x423126] ??:? void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).tryExec(scope void delegate()) [0x423070] ??:? void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).runAll() [0x4230e2] ??:? void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).tryExec(scope void delegate()) [0x423070] ??:? _d_run_main [0x422fe1] ??:? main [0x422b75] ??:? __libc_start_main [0x935bb82f] --
[Issue 16628] Special case std.algorithm.equal for known empty or infinite ranges
https://issues.dlang.org/show_bug.cgi?id=16628 Nick Treleaven changed: What|Removed |Added Keywords||pull URL||https://github.com/dlang/ph ||obos/pull/4871 --
[Issue 16628] New: Special case std.algorithm.equal for known empty or infinite ranges
https://issues.dlang.org/show_bug.cgi?id=16628 Issue ID: 16628 Summary: Special case std.algorithm.equal for known empty or infinite ranges Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW Severity: enhancement Priority: P1 Component: phobos Assignee: nob...@puremagic.com Reporter: n...@geany.org * If one of the ranges has `Range.empty == true`, we can define `equal` even when each `front` is not comparable. * If one range is known to be infinite and the other defines `length`, return false. * If both are known to be infinite, cause a compile-time error. PR pending. --
[Issue 13282] __libc_current_sigrtmax is not accessible from module linux
https://issues.dlang.org/show_bug.cgi?id=13282 Nemanja Boric <4bur...@gmail.com> changed: What|Removed |Added Status|NEW |RESOLVED CC||4bur...@gmail.com Resolution|--- |FIXED --- Comment #1 from Nemanja Boric <4bur...@gmail.com> --- This was fixed in the meantime - `SIGRTMIN` and `SIGRTMAX` are no longer aliases to a private functions: https://github.com/dlang/druntime/blob/2db828bd4f21807254b770b3ec304f14596a9805/src/core/sys/posix/signal.d#L145-L159 --
