[Issue 18033] Open in Editor button doesn't work
https://issues.dlang.org/show_bug.cgi?id=18033 --- Comment #2 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/945f894ec4e9051977a14b959fc1cca3a5515cca Fix Issue 18033 - Open in Editor button doesn't work --
[Issue 18033] Open in Editor button doesn't work
https://issues.dlang.org/show_bug.cgi?id=18033 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 9703] Failed matrix literal assignment error message
https://issues.dlang.org/show_bug.cgi?id=9703 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com --
[Issue 9703] Failed matrix literal assignment error message
https://issues.dlang.org/show_bug.cgi?id=9703 Basile B.changed: What|Removed |Added Hardware|x86 |All OS|Windows |All --
[Issue 18032] [Home] Print hex dump example doesn't run
https://issues.dlang.org/show_bug.cgi?id=18032 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/e9d845e732b2a7e284614afc9060d276fb71793e Fix Issue 18032 - [Home] Print hex dump example doesn't run https://github.com/dlang/dlang.org/commit/38f7e625567fa3aa55f95fc22b679690821d2ec7 Merge pull request #1938 from wilzbach/fix-18032 Fix Issue 18032 - [Home] Print hex dump example doesn't run merged-on-behalf-of: MetaLang--
[Issue 18032] [Home] Print hex dump example doesn't run
https://issues.dlang.org/show_bug.cgi?id=18032 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 9669] Throw in a pre-condition of a nothrow function
https://issues.dlang.org/show_bug.cgi?id=9669 Basile B.changed: What|Removed |Added Status|NEW |RESOLVED CC||b2.t...@gmx.com Hardware|x86 |All Resolution|--- |INVALID OS|Windows |All --
[Issue 9582] std.algorithm.map!(T) cause CT error for fixed size arrays
https://issues.dlang.org/show_bug.cgi?id=9582 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 5009] TraceHandler not being called on Access Violation
https://issues.dlang.org/show_bug.cgi?id=5009 Basile B.changed: What|Removed |Added Status|NEW |RESOLVED CC||b2.t...@gmx.com Resolution|--- |FIXED --
[Issue 4663] Wrong 'static' position error message
https://issues.dlang.org/show_bug.cgi?id=4663 Basile B.changed: What|Removed |Added Keywords||bootcamp CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 9181] Forward reference error in struct static fields
https://issues.dlang.org/show_bug.cgi?id=9181 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 8912] Error compiling core.memory - possible DDoc problem
https://issues.dlang.org/show_bug.cgi?id=8912 Basile B.changed: What|Removed |Added Status|NEW |RESOLVED CC||b2.t...@gmx.com Resolution|--- |WORKSFORME --
[Issue 8281] Too many error message with a failed template instantiation
https://issues.dlang.org/show_bug.cgi?id=8281 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 8277] Missed implicit cast with fixed size array
https://issues.dlang.org/show_bug.cgi?id=8277 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 7081] array slice assignment should check for opAssign
https://issues.dlang.org/show_bug.cgi?id=7081 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 6245] Using an exception object inside a delegate, causes a crash
https://issues.dlang.org/show_bug.cgi?id=6245 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com --
[Issue 7777] std.typecons.Typedef problem with global arrays
https://issues.dlang.org/show_bug.cgi?id= Basile B.changed: What|Removed |Added Status|NEW |RESOLVED CC||b2.t...@gmx.com Resolution|--- |WORKSFORME --
[Issue 7664] Problem with fixed-sized associative array key assignment
https://issues.dlang.org/show_bug.cgi?id=7664 Basile B.changed: What|Removed |Added Status|NEW |RESOLVED CC||b2.t...@gmx.com Resolution|--- |WORKSFORME --
[Issue 7224] Throwing precondition of nothrow function
https://issues.dlang.org/show_bug.cgi?id=7224 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 6657] dotProduct overload for small fixed size arrays
https://issues.dlang.org/show_bug.cgi?id=6657 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 6623] Position rigidity of @system for delegates
https://issues.dlang.org/show_bug.cgi?id=6623 Basile B.changed: What|Removed |Added CC||b2.t...@gmx.com Hardware|x86 |All OS|Windows |All --
[Issue 3720] Taking address of member functions possible without an instance
https://issues.dlang.org/show_bug.cgi?id=3720 --- Comment #11 from Mike Franklin--- A little more information about this issue and the test case: struct S { int a; void fun() { this.a = 1; } } void main() { auto fp = fp(); } There may be 2 schools of thought on how this should behave: (1) `auto fp = ` is trying to get the address of a non-static function through a type. Instead, it can be argued that the programmer should have written `S s; auto fp = ` Notice the lower-case `s`. (2) `` should return a `void function(S* s)` instead of a `void function()` If (1) were implemented the compiler would emit an error at `auto fp = ` because it is trying get the address of a non-static `fun` through the type `S`. If (2) were implemented the compiler would emit an error at `fp();` because a context pointer was not supplied as an argument. In other words it should be `fp()`. --
[Issue 2672] Delegate .funcptr returns wrong type.
https://issues.dlang.org/show_bug.cgi?id=2672 Mike Franklinchanged: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=3010 --
[Issue 3010] ICE(mtype.c) function pointer type deduction puts compiler in corrupt state
https://issues.dlang.org/show_bug.cgi?id=3010 Mike Franklinchanged: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=2672 --
[Issue 2557] inconsistent behavior when taking reference to member without instance
https://issues.dlang.org/show_bug.cgi?id=2557 Mike Franklinchanged: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --
[Issue 2557] inconsistent behavior when taking reference to member without instance
https://issues.dlang.org/show_bug.cgi?id=2557 --- Comment #11 from Mike Franklin--- I tested the test case with DMD 2.077.1 and it correctly rejects taking a reference to a non-static member function through the type Also, the "Version" for this PR is listed as "D1 (Retired)". It is my understanding that D1 is no longer supported, so closing this issue. --
[Issue 2557] inconsistent behavior when taking reference to member without instance
https://issues.dlang.org/show_bug.cgi?id=2557 Mike Franklinchanged: What|Removed |Added CC||slavo5...@yahoo.com --- Comment #10 from Mike Franklin --- For convenience, I'm adding the source code from the original post's attachment here: module method_ref; class A { void fun() {} } void main() { /* This works correctly and can sometimes be very useful */ A a = new A; void function() fn1 = void delegate() dg1; dg1.ptr = cast(void*)a; dg1.funcptr = fn1; dg1(); } class B { /+ static /* works if static */ +/ void dofun() { /* Error: this for fun needs to be type A not type method_ref.B */ A a = new A; void function() fn2 = void delegate() dg2; dg2.ptr = cast(void*)a; dg2.funcptr = fn2; dg2(); } } It can be tested online here: https://run.dlang.io/is/9GAvd4 --
[Issue 3720] Taking address of member functions possible without an instance
https://issues.dlang.org/show_bug.cgi?id=3720 Mike Franklinchanged: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=17080 --
[Issue 17080] Can assign member-function-ptr to free-function-ptr
https://issues.dlang.org/show_bug.cgi?id=17080 Mike Franklinchanged: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=3720 --
[Issue 3720] Taking address of member functions possible without an instance
https://issues.dlang.org/show_bug.cgi?id=3720 Mike Franklinchanged: What|Removed |Added CC||slavo5...@yahoo.com See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=2557 --
[Issue 2557] inconsistent behavior when taking reference to member without instance
https://issues.dlang.org/show_bug.cgi?id=2557 Mike Franklinchanged: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=3720 --
[Issue 2672] Delegate .funcptr returns wrong type.
https://issues.dlang.org/show_bug.cgi?id=2672 Mike Franklinchanged: What|Removed |Added CC||slavo5...@yahoo.com See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=3720 --
[Issue 3720] Taking address of member functions possible without an instance
https://issues.dlang.org/show_bug.cgi?id=3720 Mike Franklinchanged: What|Removed |Added See Also||https://issues.dlang.org/sh ||ow_bug.cgi?id=2672 --
[Issue 5489] std.typecons tuples dynamically iterable
https://issues.dlang.org/show_bug.cgi?id=5489 Neia Neutuladhchanged: What|Removed |Added CC||dhase...@gmail.com --- Comment #1 from Neia Neutuladh --- I just came across an instance of this: cartesianProduct( ["%a, ", "%A, ", ""], ["%d "], ["%b", "%B"], [" %Y %H:%M:%S "], ["%Z", "%z", "%.%.%.", "%.%.", "%."] ) .map!(x => joiner(x, "").array.to!string) .array I ended up using [x.tupleof], but it didn't occur to me that that was possible. I only found out about that by looking at this issue. --
[Issue 18033] Open in Editor button doesn't work
https://issues.dlang.org/show_bug.cgi?id=18033 Sebchanged: What|Removed |Added Keywords||pull Assignee|nob...@puremagic.com|greensunn...@gmail.com --- Comment #1 from Seb --- PR https://github.com/dlang/dlang.org/pull/1939 --
[Issue 18033] New: Open in Editor button doesn't work
https://issues.dlang.org/show_bug.cgi?id=18033 Issue ID: 18033 Summary: Open in Editor button doesn't work Product: D Version: D2 Hardware: x86_64 OS: All Status: NEW Severity: normal Priority: P1 Component: dlang.org Assignee: nob...@puremagic.com Reporter: greensunn...@gmail.com --
[Issue 18032] [Home] Print hex dump example doesn't run
https://issues.dlang.org/show_bug.cgi?id=18032 Sebchanged: What|Removed |Added Keywords||pull CC||greensunn...@gmail.com Assignee|nob...@puremagic.com|greensunn...@gmail.com --- Comment #1 from Seb --- PR https://github.com/dlang/dlang.org/pull/1938 --
[Issue 18032] New: [Home] Print hex dump example doesn't run
https://issues.dlang.org/show_bug.cgi?id=18032 Issue ID: 18032 Summary: [Home] Print hex dump example doesn't run Product: D Version: D2 Hardware: All URL: http://dlang.org/ OS: All Status: NEW Severity: enhancement Priority: P3 Component: dlang.org Assignee: nob...@puremagic.com Reporter: zor...@gmail.com > Application output (1: ) > Compilation output: > Program's output exceeds limit of 4096 bytes. > Program's output exceeds limit of 4096 bytes. --
[Issue 18031] Empty this compiles
https://issues.dlang.org/show_bug.cgi?id=18031 Jonathan M Davischanged: What|Removed |Added Status|NEW |RESOLVED CC||issues.dl...@jmdavisprog.co ||m Resolution|--- |INVALID --- Comment #1 from Jonathan M Davis --- It's perfectly legal to declare functions without bodies. That's what you would typically do in a .di file. The actual function body would then be in the corresponding .d file. Most of the time, there's no reason to bother with .di files, but in order for them to work, it's required that any function that does not absolutely need its body to be present be able to not have its body present (stuff like auto return functions and templated functions require their bodies, but a normal function doesn't). Similarly, in some cases, the body may be in a separate library entirely (though that's pretty much only with extern(C) functions where the D declaration is just so that the D code can use an existing C function). You'll get a linker error as soon as you try to use the function if a function body hasn't been linked in. --
[Issue 18031] Empty this compiles
https://issues.dlang.org/show_bug.cgi?id=18031 Jonathan Wilburchanged: What|Removed |Added Priority|P1 |P3 Severity|enhancement |minor --
[Issue 18031] New: Empty this compiles
https://issues.dlang.org/show_bug.cgi?id=18031 Issue ID: 18031 Summary: Empty this compiles Product: D Version: D2 Hardware: x86_64 OS: Mac OS X Status: NEW Severity: enhancement Priority: P1 Component: dmd Assignee: nob...@puremagic.com Reporter: jonathan@wilbur.space ``` public struct CommandLineInterfaceOption { immutable public string token; immutable public void function (string) callback; this (string token, void function (string) callback); } ``` This compiles, even though `this` is undefined. Is this supposed to happen? --
[Issue 14477] Nullable does not work with structs with default constructor disabled
https://issues.dlang.org/show_bug.cgi?id=14477 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --
[Issue 14477] Nullable does not work with structs with default constructor disabled
https://issues.dlang.org/show_bug.cgi?id=14477 --- Comment #5 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/61d53a1ad4a64cb5d3686c3e755bcb3508ef22f6 fix Issue 14477 - Nullable does not work with structs with default constructor disabled Add unittest, improve error message a bit. --
[Issue 18022] DDoc should place documented unittests after overloads
https://issues.dlang.org/show_bug.cgi?id=18022 --- Comment #4 from John Hall--- Okay. --
[Issue 18022] DDoc should place documented unittests after overloads
https://issues.dlang.org/show_bug.cgi?id=18022 Steven Schveighofferchanged: What|Removed |Added Keywords||ddoc --
[Issue 18022] DDoc should place documented unittests after overloads
https://issues.dlang.org/show_bug.cgi?id=18022 Steven Schveighofferchanged: What|Removed |Added Status|RESOLVED|REOPENED CC||schvei...@yahoo.com Resolution|INVALID |--- Summary|DDoc: reduce ddoc has UT|DDoc should place |between documentation |documented unittests after ||overloads --- Comment #3 from Steven Schveighoffer --- John Hall, it's not a bad suggestion, and definitely the documentation could be presented differently. However, this is functionality of the documentation generator, not phobos itself. So this would have to be an enhancement to the documentation generator, which I think you understood, but maybe the title throws people off. I'm updating the title and reopening. --
[Issue 18022] DDoc: reduce ddoc has UT between documentation
https://issues.dlang.org/show_bug.cgi?id=18022 --- Comment #2 from John Hall--- (In reply to RazvanN from comment #1) > This is not a bug, but a documented unittest. Closing as invalid. I'm not happy with this decision. I understand what a documented unittest is. The problem is the ordering. Right now, for functions like reduce, it goes 1) some template-level documentation 2) unittests 3) the functions I believe it should go 1) some template-level documentation 2) the functions 3) unittests For other examples, I noticed it in mir-algorithm, which depends on ddoc. See http://docs.algorithm.dlang.io/latest/mir_ndslice_topology.html#map the actual map function where it has the returns is all the way at the end --
[Issue 18030] New: Segmentation fault with __traits(getProtection) on template function.
https://issues.dlang.org/show_bug.cgi?id=18030 Issue ID: 18030 Summary: Segmentation fault with __traits(getProtection) on template function. Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: regression Priority: P1 Component: dmd Assignee: nob...@puremagic.com Reporter: dmdreport...@yandex.ru The following code causes dmd to crash with a segmentation fault: struct S(T) { T var; pragma( msg, "Inside S: func() is ", __traits(getProtection, __traits(getMember, T, "func")) ); } class C { alias Al = S!C; static int func(U)(U var) { return 123; } pragma( msg, "Inside C: func() is ", __traits(getProtection, __traits(getMember, C, "func")) ) } void main() {} $ dmd app.d Inside S: func() is Segmentation fault This error first appeared in dmd2.075. Here is a simple test project on github and tests results from travis-ci. https://github.com/Betelgeyser/getprotectionbug https://travis-ci.org/Betelgeyser/getprotectionbug If C.func() has no template parameters or __traits(getProtection) is not called inside struct S, then the code compiles. Calling __traits(getProtection) inside class C does not result in a segfault. Whether S and C are classes or structs does not affect this error. --
[Issue 5351] Add template mixin for Range Primitives using random access
https://issues.dlang.org/show_bug.cgi?id=5351 Simen Kjaeraaschanged: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from Simen Kjaeraas --- isRandomAccessRange is a compile-time construct, and checking foo[0] == foo.front is generally not possible at compile-time. Even if it is, the fact they're equal right now doesn't mean they always will be (consider the fibonacci sequence 1,1,2,3,5,8,13,21..., which would have foo[0] == foo.front after one popFront, but not two). In addition, as you say, having an indexable range with semantics different from random access ranges is not at all desirable, and a recipe for disaster at some later point. I agree having this kind of functionality in Phobos would be nice, but I don't see a workable path to that goal. I'm closing this - please reopen if there are revelations that make it possible in the future. --