[Issue 17955] compiler segfault in DsymbolSemanticVisitor::visit(UnittestDeclaration*)
https://issues.dlang.org/show_bug.cgi?id=17955 Walter Bright changed: What|Removed |Added Keywords||ice-on-invalid-code --
[Issue 17955] compiler segfault in DsymbolSemanticVisitor::visit(UnittestDeclaration*)
https://issues.dlang.org/show_bug.cgi?id=17955 Walter Bright changed: What|Removed |Added CC||bugzi...@digitalmars.com --- Comment #1 from Walter Bright --- https://github.com/dlang/dmd/pull/7277 --
[Issue 12507] SysTime.init.toString should not segfault
https://issues.dlang.org/show_bug.cgi?id=12507 --- Comment #10 from Rob T --- I just encounter this issue and spent an hour or so figuring out what the cause was. segfaults tend to be very difficult to track down and deal with. A quick sub-optimal fix will be better than leaving it to seg fault. --
[Issue 12507] SysTime.init.toString should not segfault
https://issues.dlang.org/show_bug.cgi?id=12507 Rob T changed: What|Removed |Added CC||al...@ucora.com --
[Issue 481] Letting compiler determine length for fixed-length arrays
https://issues.dlang.org/show_bug.cgi?id=481 --- Comment #42 from Andrei Alexandrescu --- (In reply to RazvanN from comment #41) > should this be closed? Let's keep it open until a library implementation is merged. I'll change the title. --
[Issue 481] Fixed-length arrays with automatically computed length
https://issues.dlang.org/show_bug.cgi?id=481 Andrei Alexandrescu changed: What|Removed |Added Summary|Letting compiler determine |Fixed-length arrays with |length for fixed-length |automatically computed |arrays |length --
[Issue 16313] Duplicate symbol generated
https://issues.dlang.org/show_bug.cgi?id=16313 --- Comment #3 from Jorge Lima --- (In reply to RazvanN from comment #2) > Just tested on Windows with git HEAD and the issue is still present. On > Ubuntu 16.04 the issue is not present. Changing description to Windows I tested before with release 2.072.0 and the problem was fixed. See my previous comment from 2016-11-25. However. at the time, I didn't check on all platforms Triggered by your comment, I tested now the release 2.076.1 on the following platforms Ubuntu 16.04 64bit: passed OS X 10.10: passed Windows 10 64bit: failed but due to a different issue. See below. > dmd snippet.d OPTLINK (R) for Win32 Release 8.00.17 Copyright (C) Digital Mars 1989-2013 All rights reserved. http://www.digitalmars.com/ctg/optlink.html teste.obj(teste) Offset 00370H Record Type 009D Error 16: Index Range Error: linker exited with status 1 I noticed OPTLINK is for Win32. Weird! So I passed the option -m64 to dmd to force it to use the microsoft linker. > dmd -m64 snippet.d And it compiled the snippet without errors. So I would say this problem seems to be fixed! --
[Issue 13041] std.range.transposed consumes sub-ranges
https://issues.dlang.org/show_bug.cgi?id=13041 --- Comment #3 from hst...@quickfur.ath.cx --- I wonder if there's any possibility of implementing .save for a random-access range, if the subranges are also random-access. In this case, we wouldn't need to consume the subranges at all, but can simply store a set of current indices to implement .transposed. --
[Issue 780] (D1 only) The assignment of 'this' is allowed
https://issues.dlang.org/show_bug.cgi?id=780 Steven Schveighoffer changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #8 from Steven Schveighoffer --- Reopening, this is a D1 only bug. I'm not in a position to test, but I can't tell if you mean that you tested on the HEAD for D1 or not. I can't imagine this got fixed by accident in D1. --
[Issue 13041] std.range.transposed consumes sub-ranges
https://issues.dlang.org/show_bug.cgi?id=13041 Steven Schveighoffer changed: What|Removed |Added Status|NEW |RESOLVED CC||schvei...@yahoo.com Resolution|--- |WONTFIX --- Comment #2 from Steven Schveighoffer --- Given how issue 17952 was resolved (we deprecated transposed being a forward range, as it would require dup'ing per save), I think we can close this as WONTFIX. Once Transposed.save is removed, we can update the docs to reflect that transposed may consume sub-ranges. I think this is just in the nature of transposed and how forward ranges are stored. --
[Issue 17952] std.range.transposed save is invalid
https://issues.dlang.org/show_bug.cgi?id=17952 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 17952] std.range.transposed save is invalid
https://issues.dlang.org/show_bug.cgi?id=17952 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/cd55be3311cee1ab9a0dbcb5fc4ef56374b9c7aa Fix Issue 17952 - std.range.transposed save is invalid https://github.com/dlang/phobos/commit/fec4b60ce6003c311bdb8e348d42be825d0625fa Merge pull request #5832 from Darredevil/issue-17952-transposed-save Fix Issue 17952 - std.range.transposed save is invalid merged-on-behalf-of: Andrei Alexandrescu --
[Issue 5044] opIndexUnary not working for post++
https://issues.dlang.org/show_bug.cgi?id=5044 b2.t...@gmx.com changed: What|Removed |Added CC||b2.t...@gmx.com --
[Issue 17959] [DIP1000] Can store scope delegate in non-scope member
https://issues.dlang.org/show_bug.cgi?id=17959 Mathias Lang changed: What|Removed |Added Keywords||safe --
[Issue 17959] New: [DIP1000] Can store scope delegate in non-scope member
https://issues.dlang.org/show_bug.cgi?id=17959
Issue ID: 17959
Summary: [DIP1000] Can store scope delegate in non-scope member
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P1
Component: dmd
Assignee: nob...@puremagic.com
Reporter: mathias.l...@sociomantic.com
The following segfault:
```
class Foo
{
private void delegate () @safe escape;
void esc () @safe scope
{
this.escape = &this.esc;
}
}
void main () @safe
{
auto x2 = bar();
assert(x2 !is null);
x2();
}
void delegate() @safe bar () @safe
{
scope o = new Foo;
o.esc;
return o.escape;
}
```
I'd except the assignment in esc to fail.
Tested with v2.076.1 and f3446967d
--
[Issue 780] (D1 only) The assignment of 'this' is allowed
https://issues.dlang.org/show_bug.cgi?id=780 RazvanN changed: What|Removed |Added Status|ASSIGNED|RESOLVED CC||razvan.nitu1...@gmail.com Resolution|--- |FIXED --- Comment #7 from RazvanN --- Running the original example on git HEAD on an Ubuntu 16.04 machine results in compilation failure with the message "This is not an lvalue". Closing as fixed. --
[Issue 481] Letting compiler determine length for fixed-length arrays
https://issues.dlang.org/show_bug.cgi?id=481 RazvanN changed: What|Removed |Added CC||razvan.nitu1...@gmail.com --- Comment #41 from RazvanN --- should this be closed? --
[Issue 144] Alias and function names fail to collide
https://issues.dlang.org/show_bug.cgi?id=144
RazvanN changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC||razvan.nitu1...@gmail.com
Resolution|--- |INVALID
--- Comment #4 from RazvanN ---
This is not a bug, it's the desired behavior since alias is used to include
functions in the same overload set. It can't issue an error when an alias has
the same name as a function, otherwise it would be impossible to bring other
functions to the overload set.
For example: if you have 3 foo overloads:
void foo() {}
void foo(int a) {}
void foo(int a, int b) {}
and you want to bring an imported function in the same overload set you do:
alias foo = path.to.import.foo
The problem in your example is that the 2 functions you bring in the same
overload set have the exact same signature and are in the same file. So the
compiler let's alias your function because it thinks you want to have the in
the same overload set, but when you try to call it, it issues an error because
it does not know which one it should call. This is correct behavior.
Closing as invalid.
--
[Issue 17607] not an associative array initializer
https://issues.dlang.org/show_bug.cgi?id=17607 Andre changed: What|Removed |Added Severity|enhancement |normal --
[Issue 17958] Crypto interface in phobos
https://issues.dlang.org/show_bug.cgi?id=17958 --- Comment #1 from Andre --- *** Issue 16510 has been marked as a duplicate of this issue. *** --
[Issue 16510] Request: RSA digital signature validation in phobos
https://issues.dlang.org/show_bug.cgi?id=16510 Andre changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Andre --- Superseded by https://issues.dlang.org/show_bug.cgi?id=17958 *** This issue has been marked as a duplicate of issue 17958 *** --
[Issue 17958] New: Crypto interface in phobos
https://issues.dlang.org/show_bug.cgi?id=17958 Issue ID: 17958 Summary: Crypto interface in phobos Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P1 Component: phobos Assignee: nob...@puremagic.com Reporter: an...@s-e-a-p.de In discussion https://forum.dlang.org/thread/osnema$d5s$1...@digitalmars.com it became clear, including crypto logic into phobos might be a pandora box and should be avoided. An alternative is to provide a crypto interface within phobos with implementations for SChannel (windows api), mbedtls, openssl, ... As a starting point, I am interested in RSA Digital Signature Validation but The crypto interface should be open for any algorithm. --
[Issue 16313] Duplicate symbol generated
https://issues.dlang.org/show_bug.cgi?id=16313 RazvanN changed: What|Removed |Added CC||razvan.nitu1...@gmail.com OS|Mac OS X|Windows --- Comment #2 from RazvanN --- Just tested on Windows with git HEAD and the issue is still present. On Ubuntu 16.04 the issue is not present. Changing description to Windows --
[Issue 17943] Wrong pointer arithmetic optimization
https://issues.dlang.org/show_bug.cgi?id=17943 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to stable at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/b8a263d2aa7a2091d95dc6f57fd06f1315b5c9fa Fix issue 17943 - Wrong pointer arithmetic optimization store result as llong. https://github.com/dlang/dmd/commit/a244ac72197211d94be965ce09a5f84be2ac09e4 Merge pull request #7269 from yshui/17943 Fix issue 17943 - Wrong pointer arithmetic optimization merged-on-behalf-of: Martin Nowak --
[Issue 17943] Wrong pointer arithmetic optimization
https://issues.dlang.org/show_bug.cgi?id=17943 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 17167] dmd fails to write to file or create directory with more than 248 characters in the path
https://issues.dlang.org/show_bug.cgi?id=17167 --- Comment #2 from Atila Neves --- After some investigation, it seems that dub specifying relative paths makes it more likely to pass the 248 character limit, since Windows first appends the current absolute path to the relative one. This is a known Windows limitation up until an opt-in in Windows 10 to make the problem go away, and otherwise has to be dealt with by calling the Unicode-aware Win32 file APIs. --
[Issue 16461] Using the fully qualified type of an object within its own scope causes an error
https://issues.dlang.org/show_bug.cgi?id=16461 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC||razvan.nitu1...@gmail.com Resolution|--- |FIXED --- Comment #3 from RazvanN --- I guess we can mark this as fixed. Please open a new bug report if you track down the new issue. --
[Issue 16467] templated function default argument take into account when not needed
https://issues.dlang.org/show_bug.cgi?id=16467 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC||razvan.nitu1...@gmail.com Resolution|--- |WONTFIX --
[Issue 15970] C++ mangling of templated arg type
https://issues.dlang.org/show_bug.cgi?id=15970 Johan Engelen changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|INVALID |--- --- Comment #4 from Johan Engelen --- Read the bug report carefully before discarding it. The argument type is currently "A" (wrong), instead of "Symbol*" --
[Issue 17167] dmd fails to write to file or create directory with more than 248 characters in the path
https://issues.dlang.org/show_bug.cgi?id=17167 Atila Neves changed: What|Removed |Added Summary|dmd fails to write to file |dmd fails to write to file |with 6 or more ".." in the |or create directory with |path|more than 248 characters in ||the path --
[Issue 17167] dmd fails to write to file with 6 or more ".." in the path
https://issues.dlang.org/show_bug.cgi?id=17167 Atila Neves changed: What|Removed |Added CC||lae...@laeeth.com --- Comment #1 from Atila Neves --- *** Issue 17888 has been marked as a duplicate of this issue. *** --
[Issue 17888] dmd fails on Windows if path is too long
https://issues.dlang.org/show_bug.cgi?id=17888 Atila Neves changed: What|Removed |Added Status|NEW |RESOLVED CC||atila.ne...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Atila Neves --- *** This issue has been marked as a duplicate of issue 17167 *** --
[Issue 16649] Header gen skips parens
https://issues.dlang.org/show_bug.cgi?id=16649 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from RazvanN --- As the above PR has been merged and the fix is available in HEAD dev branch, I'll close this as resolved. If there is urgent need for this fix, please copy paste the fix from the PR, it's a one liner. --
[Issue 14956] C++ Mangling incompatible with C++11
https://issues.dlang.org/show_bug.cgi?id=14956
--- Comment #12 from Walter Bright ---
(In reply to Sahmi Soulaïman (سليمان السهمي) from comment #10)
> std::base_string!char func() {}
The code is neither C++ nor D. Please provide an accurate code example, what it
mangles to, and what it should mangle to. Thanks!
--
[Issue 14956] C++ Mangling incompatible with C++11
https://issues.dlang.org/show_bug.cgi?id=14956 --- Comment #11 from Walter Bright --- I'm not sure this is actually a D compiler problem. If, on the D side, basic_string is aliased to __cxx11::basic_string, it should mangle correctly. This is pointed out in Comment 4. --
[Issue 16289] no extern(C++) mangling for size_t/unsigned long parameters
https://issues.dlang.org/show_bug.cgi?id=16289 --- Comment #2 from Walter Bright --- Sometimes I just make the C++ function `extern "C"` and that works. --
[Issue 15970] C++ mangling of templated arg type
https://issues.dlang.org/show_bug.cgi?id=15970 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Walter Bright --- In C++, class types are not reference types. In D they are, and D represents the reference type as a pointer type when translating to C++. The result is what you see, Symbol* instead of Symbol when looking at the C++ mangling. This is working as intended. --
