Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 04:46:18 UTC, Jonathan M Davis wrote: Pretty much the worst that happens is you accidentally use a member variable directly instead of using a property function to access it, and that's rarely a big deal. Often, it's even desirable. I'll keep that argument for the

Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 04:46:18 UTC, Jonathan M Davis wrote: If you really insist on the viewpoint that class encapsulation means that nothing outside of that class can access any of its private members, then what D does definitely breaks encapsulation. But having friends in C++ already

Re: LDC 1.10.0 beta

On Monday, 14 May 2018 at 18:31:13 UTC, Jacob Carlborg wrote: On 2018-05-13 20:12, kinke wrote: Hi everyone, on behalf of the LDC team, I'm glad to announce the first beta for LDC 1.10. The highlights of this version in a nutshell: * Based on D 2.080.0. * Supports DragonFly BSD. * Some

Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 04:22:30 UTC, Mike Parker wrote: On Tuesday, 15 May 2018 at 02:32:05 UTC, KingJoffrey wrote: - Object independence - Do not violate encapsulation - Respect the interface This is what I don't get from your position. What is encapsulation? Here's what Wikipedia

Re: Sealed classes - would you want them in D?

On Tuesday, May 15, 2018 04:22:30 Mike Parker via Digitalmars-d wrote: > On Tuesday, 15 May 2018 at 02:32:05 UTC, KingJoffrey wrote: > > - Object independence > > - Do not violate encapsulation > > - Respect the interface > > This is what I don't get from your position. What is > encapsulation?

Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 02:32:05 UTC, KingJoffrey wrote: - Object independence - Do not violate encapsulation - Respect the interface This is what I don't get from your position. What is encapsulation? Here's what Wikipedia says [1]: "Encapsulation is used to hide the values or state

Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 03:32:22 UTC, Norm wrote: I'm seeing the opposite, more and more large applications adopting Python as much as possible and replacing big chunks of the C++ core and leaving only those C++ chunks where performance is all that really matters. Encapsulation

[Issue 18847] std.allocator: Region uses .parent before it can be set

https://issues.dlang.org/show_bug.cgi?id=18847 Vladimir Panteleev changed: What|Removed |Added Assignee|nob...@puremagic.com

[Issue 18847] std.allocator: Region uses .parent before it can be set

https://issues.dlang.org/show_bug.cgi?id=18847 --- Comment #1 from Vladimir Panteleev --- Some goes for BitmappedBlock and KKRegion. ContiguousFreeList seems to have gotten this right (though with the end result of having 8 constructor declarations). --

Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 02:32:05 UTC, KingJoffrey wrote: On Tuesday, 15 May 2018 at 02:00:17 UTC, 12345swordy wrote: On Tuesday, 15 May 2018 at 00:28:42 UTC, KingJoffrey wrote: On Monday, 14 May 2018 at 19:40:18 UTC, 12345swordy wrote: A slippery slope fallacy isn't helping your case.

[Issue 18860] New: Destructors and postblit constructors do not appear in DDoc output

https://issues.dlang.org/show_bug.cgi?id=18860 Issue ID: 18860 Summary: Destructors and postblit constructors do not appear in DDoc output Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 02:00:17 UTC, 12345swordy wrote: On Tuesday, 15 May 2018 at 00:28:42 UTC, KingJoffrey wrote: On Monday, 14 May 2018 at 19:40:18 UTC, 12345swordy wrote: A slippery slope fallacy isn't helping your case. Write a DIP if it bothers you so much, as it changes the

Re: Wait-free MPSC and MPMC implement in D

On Wednesday, 9 May 2018 at 04:17:17 UTC, Shachar Shemesh wrote: On 09/05/18 01:09, David Nadlinger wrote: The algorithm isn't wait-free (haven't thought too carefully about this, though) This mirrors a discussion I had with Maor (who originally wrote it). Let's see if I bring you around the

Re: returning and receiving multiple values from a function

On Tuesday, 15 May 2018 at 01:40:50 UTC, timepp wrote: Now C++ allow this in a very clean way: std::tuple foo() { return {128, true, 1.5f}; } auto [value1, value2, value3] = foo(); Would D plan to support that in syntax level? it depends if some dip like

Re: Sealed classes - would you want them in D?

On Tuesday, 15 May 2018 at 00:28:42 UTC, KingJoffrey wrote: On Monday, 14 May 2018 at 19:40:18 UTC, 12345swordy wrote: A slippery slope fallacy isn't helping your case. Write a DIP if it bothers you so much, as it changes the languages fundamentally. Alexander If 'getting a module to

returning and receiving multiple values from a function

Now C++ allow this in a very clean way: std::tuple foo() { return {128, true, 1.5f}; } auto [value1, value2, value3] = foo(); Would D plan to support that in syntax level?

[Issue 18821] DMD segfault 2.080

https://issues.dlang.org/show_bug.cgi?id=18821 --- Comment #6 from Walter Bright --- Thank you. I was able to reproduce the problem. --

[Issue 18859] Silence class allocator/deallocator deprecation warning if they are marked "deprecated"

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

[Issue 18859] Silence class allocator/deallocator deprecation warning if they are marked "deprecated"

https://issues.dlang.org/show_bug.cgi?id=18859 --- Comment #2 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/b6f92b288a005c5334793b318c1bf2ab70152ed4 Fix Issue 18859 - Silence class allocator/deallocator

Re: Sealed classes - would you want them in D?

On Monday, 14 May 2018 at 19:40:18 UTC, 12345swordy wrote: A slippery slope fallacy isn't helping your case. Write a DIP if it bothers you so much, as it changes the languages fundamentally. Alexander If 'getting a module to respect the enscapsulation boundaries the programmer puts in

[Issue 18859] Silence class allocator/deallocator deprecation warning if they are marked "deprecated"

https://issues.dlang.org/show_bug.cgi?id=18859 Vladimir Panteleev changed: What|Removed |Added Keywords||pull

Re: The #dbugfix Campaign Round 1 Report

On Monday, 14 May 2018 at 17:22:11 UTC, 12345swordy wrote: Be sure to post it in r/programming This sort of community-centric post doesn't belong there. We have to be careful not to reinforce the perception that we're spamming the sub.

Re: Sealed classes - would you want them in D?

On 5/14/2018 1:32 AM, Piotr Mitana wrote: OK, Walter, point for you for this :) Welcs!

Re: `free` for struct with C bindings.

On 05/14/2018 03:03 PM, Jonathan wrote: Do I need to call the `free` function with my D code because I need to free memory that was allocated in C code? Yes, you have to free the memory with C's free(): void main() { import core.stdc.stdlib; auto p = malloc(42); free(p); } Ali

Re: `free` for struct with C bindings.

On 05/15/2018 12:03 AM, Jonathan wrote: ``` xcb_generic_event_t*    event; event = xcb_wait_for_event (connection); free (event); ``` The problem is the `free` function.  It is not provided by the library but is part of the C standard library (in stdlib.h). D has the C functions in

[Issue 18859] New: Silence class allocator/deallocator deprecation warning if they are marked "deprecated"

https://issues.dlang.org/show_bug.cgi?id=18859 Issue ID: 18859 Summary: Silence class allocator/deallocator deprecation warning if they are marked "deprecated" Product: D Version: D2 Hardware: All OS: All

`free` for struct with C bindings.

I am using a C bindings library (https://code.dlang.org/packages/xcb-d). I am following through a tutorial that was written for the C library directly and just making the minor changes to make it work with D. I ran into a problem. The library ends up giving me a struct pointer. ```

[Issue 18858] switch 'skips declaration' test only checks last declaration

https://issues.dlang.org/show_bug.cgi?id=18858 --- Comment #1 from Walter Bright --- https://github.com/dlang/dmd/pull/8246 --

[Issue 18821] DMD segfault 2.080

https://issues.dlang.org/show_bug.cgi?id=18821 ag0aep6g changed: What|Removed |Added Keywords||ice --

[Issue 18821] DMD segfault 2.080

https://issues.dlang.org/show_bug.cgi?id=18821 ag0aep6g changed: What|Removed |Added CC||ag0ae...@gmail.com ---

DCD 0.9.7 is available

See [1]. with mostly (since v0.9.4) two possible `RangeError` fixed, completion on the `IfCondition` variables [2] (which was surprisingly not at all implemented), and freeze fixed on the windows version (32 bit OMF), which forced to build with an older DMD version. All binaries are

[Issue 18858] New: switch 'skips declaration' test only checks last declaration

https://issues.dlang.org/show_bug.cgi?id=18858 Issue ID: 18858 Summary: switch 'skips declaration' test only checks last declaration Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: Sealed classes - would you want them in D?

On Monday, 14 May 2018 at 07:44:00 UTC, KingJoffrey wrote: D may as well just get rid of that encapsulation concept too, since the class interface is pretty much moot in D modules. Maybe.. we should even, just completely get rid of functions and classes - as well as all that other stupid

[Issue 18606] [REG2.072] "cannot append type const(T) to type T[]" in .dup

https://issues.dlang.org/show_bug.cgi?id=18606 --- Comment #2 from Vladimir Panteleev --- The commits are big too, but if it helped, I can bisect it down to the commit. --

[Issue 18712] [Reg 2.072] bogus "switch skips declaration" error with case in mixin

https://issues.dlang.org/show_bug.cgi?id=18712 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

Re: Bug?: Presence of "init()" Method Causes std.array.appender to Fail to Compile

On Monday, May 14, 2018 18:29:33 David Nadlinger via Digitalmars-d wrote: > On Monday, 14 May 2018 at 11:53:44 UTC, Nick Treleaven wrote: > > On Monday, 14 May 2018 at 01:20:38 UTC, Jonathan M Davis wrote: > >> Yeah. It's been discussed that it should be illegal to declare > >> a struct or class

Re: LDC 1.10.0 beta

On Monday, 14 May 2018 at 18:31:13 UTC, Jacob Carlborg wrote: Out of curiosity, how come the Objective-C integration seem to always lack behind when LDC merges a new DMD release with some new Objective-C integration? Is it less prioritized, not so much knowledge in this area, something else?

Re: Bug?: Presence of "init()" Method Causes std.array.appender to Fail to Compile

On Monday, 14 May 2018 at 11:53:44 UTC, Nick Treleaven wrote: On Monday, 14 May 2018 at 01:20:38 UTC, Jonathan M Davis wrote: Yeah. It's been discussed that it should be illegal to declare a struct or class member named init, but that change has yet to happen.

Re: Dependency injection pattern

On 05/13/2018 12:42 AM, Suliman wrote: Could anybody give small example of Dependency injection pattern? I googled about it, but found only C# examples and I am not quite sure how to use them. Also I would like get some explanation/comments for code. The name and the unnecessary confusion

Re: The #dbugfix Campaign Round 1 Report

On 15/05/2018 5:22 AM, 12345swordy wrote: On Monday, 14 May 2018 at 15:23:41 UTC, Mike Parker wrote: I planned an extended vacation with my wife around DConf this year and, despite my intentions before we left, fell quite far behind on my D duties. I'm in the process of getting caught up with

Re: The #dbugfix Campaign Round 1 Report

On Monday, 14 May 2018 at 15:23:41 UTC, Mike Parker wrote: I planned an extended vacation with my wife around DConf this year and, despite my intentions before we left, fell quite far behind on my D duties. I'm in the process of getting caught up with everything, and that includes publishing

[Issue 18821] DMD segfault 2.080

https://issues.dlang.org/show_bug.cgi?id=18821 --- Comment #4 from Mr. Smith --- Reduced to this: ``` module test18821; import std.experimental.allocator : makeArray; import core.sys.linux.epoll; class MmapPool { static MmapPool instance() { return null;

[Issue 18850] Template overload incorrectly results in recursive expansion error

https://issues.dlang.org/show_bug.cgi?id=18850 Jonathan Marler changed: What|Removed |Added Status|NEW |RESOLVED

Re: Sealed classes - would you want them in D?

On Monday, 14 May 2018 at 07:59:06 UTC, Jonathan M Davis wrote: On Monday, May 14, 2018 07:03:35 Dukc via Digitalmars-d wrote: On Monday, 14 May 2018 at 07:02:37 UTC, Dukc wrote: module test; void main() { foo.i = 2; } void foo() { static int i = 1; } If that's what

The #dbugfix Campaign Round 1 Report

I planned an extended vacation with my wife around DConf this year and, despite my intentions before we left, fell quite far behind on my D duties. I'm in the process of getting caught up with everything, and that includes publishing the results of the first round of the #dbugfix campaign.

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 Mike Franklin changed: What|Removed |Added See Also|

[Issue 12228] Identifiers 'this' and 'super' should not be allowed as base classes

https://issues.dlang.org/show_bug.cgi?id=12228 Mike Franklin changed: What|Removed |Added See Also|

[Issue 6579] Calling static method should *require* using type and not instance, unless specified by author

https://issues.dlang.org/show_bug.cgi?id=6579 Mike Franklin changed: What|Removed |Added See Also|

[Issue 14170] `this` compiles in a static context

https://issues.dlang.org/show_bug.cgi?id=14170 Mike Franklin changed: What|Removed |Added See Also|

[Issue 18821] DMD segfault 2.080

https://issues.dlang.org/show_bug.cgi?id=18821 --- Comment #3 from Mr. Smith --- Created attachment 1694 --> https://issues.dlang.org/attachment.cgi?id=1694=edit Stack trace --

[Issue 18821] DMD segfault 2.080

https://issues.dlang.org/show_bug.cgi?id=18821 --- Comment #2 from Mr. Smith --- Looks like the issue was with dlib library Uploaded stacktrace as attachment Will try reducing code. --

Re: iopipe v0.0.4 - RingBuffers!

On Thursday, 10 May 2018 at 23:22:02 UTC, Steven Schveighoffer wrote: However, I am struggling to find a use case for this that showcases why you would want to use it. While it does work, and works beautifully, it doesn't show any measurable difference vs. the array allocated buffer that

[Issue 18600] Regex performance enhancement for repeated matchFirst calls

https://issues.dlang.org/show_bug.cgi?id=18600 --- Comment #2 from Jon Degenhardt --- Phobos PR 6268 was included in LDC 1.10.0-beta1. For this release the standard benchmark I used for the TSV Utilities improved as follows: LDC 1.7.0 (before regression): 8.37

[Issue 18833] [REG 2.073] DMD in some cases forgets to generate wrapping TypeInfo for modifiers on classes

https://issues.dlang.org/show_bug.cgi?id=18833 --- Comment #2 from Steven Schveighoffer --- I assumed since I reduced this from issue 17968 that it has the same regression point (i.e. 2.073 is when it regressed). I just now tested locally and indeed, 2.073.0 shows the

[Issue 18114] [Reg 2.078] regex performance regression

https://issues.dlang.org/show_bug.cgi?id=18114 --- Comment #9 from Jon Degenhardt --- The final performance fix was included in LDC 1.10.0-beta1. For this release the standard benchmark I used for the TSV Utilities improved as follows: LDC 1.7.0 (before

Re: iopipe v0.0.4 - RingBuffers!

On 5/14/18 6:02 AM, bioinfornatics wrote: On Thursday, 10 May 2018 at 23:22:02 UTC, Steven Schveighoffer wrote: OK, so at dconf I spoke with a few very smart guys about how I can use mmap to make a zero-copy buffer. And I implemented this on the plane ride home. However, I am struggling to

[Issue 18712] [Reg 2.072] bogus "switch skips declaration" error with case in mixin

https://issues.dlang.org/show_bug.cgi?id=18712 Walter Bright changed: What|Removed |Added CC|

[Issue 16527] extern( C++ ) Win64 build - return struct by value is broken

https://issues.dlang.org/show_bug.cgi?id=16527 Ethan Watson changed: What|Removed |Added Status|NEW |RESOLVED

Re: Is D releasing too often?

On Monday, 14 May 2018 at 07:20:48 UTC, Joakim wrote: I thought I'd open it up to the community: now that you've experienced this faster pace, as a user of the D compilers, how do you like it? Would you prefer a slower release schedule, say 3-4 major releases a year? I would prefer to have

[Issue 18606] [REG2.072] "cannot append type const(T) to type T[]" in .dup

https://issues.dlang.org/show_bug.cgi?id=18606 --- Comment #1 from Walter Bright --- (In reply to Vladimir Panteleev from comment #0) > Introduced in https://github.com/dlang/dmd/pull/5500 This is why I don't like 700 line PRs spread across 18 files :-( --

[Issue 1412] stringof shouldn't be shadowed by member func

https://issues.dlang.org/show_bug.cgi?id=1412 Nick Treleaven changed: What|Removed |Added Status|REOPENED|RESOLVED

[Issue 7066] You can redefine .init and .stringof without error

https://issues.dlang.org/show_bug.cgi?id=7066 Nick Treleaven changed: What|Removed |Added CC||dav...@126.com --- Comment

Identifier from string - Re: static foreach considered

On Monday, 8 June 2015 at 21:32:52 UTC, Timon Gehr wrote: On 06/08/2015 10:16 PM, Idan Arye wrote: It would be nice together with this feature to be able to mixin identifiers: static foreach (ident; ["foo", "bar"]) { auto mixin(ident)() { // code for

[Issue 18473] [Reg 2.078.1] std.math.approxEqual no longer accepts nested ranges

https://issues.dlang.org/show_bug.cgi?id=18473 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18833] [REG 2.073] DMD in some cases forgets to generate wrapping TypeInfo for modifiers on classes

https://issues.dlang.org/show_bug.cgi?id=18833 Walter Bright changed: What|Removed |Added CC|

[Issue 14170] `this` compiles in a static context

https://issues.dlang.org/show_bug.cgi?id=14170 Simen Kjaeraas changed: What|Removed |Added CC|

[Issue 18821] DMD segfault 2.080

https://issues.dlang.org/show_bug.cgi?id=18821 Walter Bright changed: What|Removed |Added CC|

[Issue 2698] Syntax to parse an identifier from a string, instead of mixin()

https://issues.dlang.org/show_bug.cgi?id=2698 Nick Treleaven changed: What|Removed |Added Summary|Parameterised identifier|Syntax to parse an

[Issue 2698] Parameterised identifier

https://issues.dlang.org/show_bug.cgi?id=2698 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org --- Comment

[Issue 14064] Error message about @ attributes incomplete.

https://issues.dlang.org/show_bug.cgi?id=14064 Nick Treleaven changed: What|Removed |Added Keywords||trivial

[Issue 15501] Missing parens for template argument in error message: Error: no property 'nsecs' for type 'MonoTimeImpl!cast(ClockType)0'

https://issues.dlang.org/show_bug.cgi?id=15501 Nick Treleaven changed: What|Removed |Added Keywords||trivial

[Issue 14854] @disable this inconsistent between structs and classes

https://issues.dlang.org/show_bug.cgi?id=14854 Nick Treleaven changed: What|Removed |Added Keywords||trivial

[Issue 12228] Identifiers 'this' and 'super' should not be allowed as base classes

https://issues.dlang.org/show_bug.cgi?id=12228 Nick Treleaven changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 14170] `this` compiles in a static context

https://issues.dlang.org/show_bug.cgi?id=14170 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org

[Issue 8162] [TDPL] -property fails to give an error when a property function is called with parens

https://issues.dlang.org/show_bug.cgi?id=8162 --- Comment #7 from Nick Treleaven --- *** Issue 7307 has been marked as a duplicate of this issue. *** --

[Issue 7307] Not fully enforced properties syntax

https://issues.dlang.org/show_bug.cgi?id=7307 Nick Treleaven changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18857] New: [std.experimental.logger] use NullLogger as the default

https://issues.dlang.org/show_bug.cgi?id=18857 Issue ID: 18857 Summary: [std.experimental.logger] use NullLogger as the default Product: D Version: D2 Hardware: x86 OS: Windows Status: NEW

Re: Bug?: Presence of "init()" Method Causes std.array.appender to Fail to Compile

On Monday, 14 May 2018 at 01:20:38 UTC, Jonathan M Davis wrote: Yeah. It's been discussed that it should be illegal to declare a struct or class member named init, but that change has yet to happen. https://issues.dlang.org/show_bug.cgi?id=7066 Walter and Timon have considered redefinition

[Issue 8161] -property should give an error for invalid property functions

https://issues.dlang.org/show_bug.cgi?id=8161 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org --- Comment

[Issue 7066] You can redefine .init and .stringof without error

https://issues.dlang.org/show_bug.cgi?id=7066 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org --- Comment

[Issue 14237] Compiler should reject attempts to (re)define .init

https://issues.dlang.org/show_bug.cgi?id=14237 Nick Treleaven changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 13943] Grammar does not list 'super' and 'this' as types

https://issues.dlang.org/show_bug.cgi?id=13943 Mike Franklin changed: What|Removed |Added Keywords||pull

[Issue 7066] You can redefine .init and .stringof without error

https://issues.dlang.org/show_bug.cgi?id=7066 Nick Treleaven changed: What|Removed |Added CC||heartcollector...@gmail.com

[Issue 12228] Identifiers 'this' and 'super' should not be allowed as base classes

https://issues.dlang.org/show_bug.cgi?id=12228 Nick Treleaven changed: What|Removed |Added See Also||https://issues.dlang.org/sh

[Issue 13943] Grammar does not list 'super' and 'this' as types

https://issues.dlang.org/show_bug.cgi?id=13943 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org

Re: serialport v1.0.0

On Sun, 2018-05-13 at 12:05 -0600, Jonathan M Davis via Digitalmars-d-announce wrote: […] > > Really? If the consensus is that it should go in, then okay, but I don't > think that I've ever seen a standard library with anything like > functionality for talking to serial ports. And what would

[Issue 12228] Identifiers 'this' and 'super' should not be allowed as base classes

https://issues.dlang.org/show_bug.cgi?id=12228 Nick Treleaven changed: What|Removed |Added CC||n...@geany.org --- Comment

[Issue 6454] @property doesn't need return type

https://issues.dlang.org/show_bug.cgi?id=6454 Nick Treleaven changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 18853] std.allocator: AllocatorList fails to allocate after a deallocation

https://issues.dlang.org/show_bug.cgi?id=18853 alex.jercai...@gmail.com changed: What|Removed |Added CC||alex.jercai...@gmail.com

Re: D GPU execution module: A survey of requirements.

On Thursday, 10 May 2018 at 07:25:32 UTC, Nicholas Wilson wrote: On Thursday, 10 May 2018 at 00:10:07 UTC, H Paterson wrote: On Wednesday, 9 May 2018 at 23:37:14 UTC, Henry Gouk wrote: On Wednesday, 9 May 2018 at 23:26:19 UTC, H Paterson wrote: Hello, I'm interested in writing a module for

Re: iopipe v0.0.4 - RingBuffers!

On Thursday, 10 May 2018 at 23:22:02 UTC, Steven Schveighoffer wrote: OK, so at dconf I spoke with a few very smart guys about how I can use mmap to make a zero-copy buffer. And I implemented this on the plane ride home. However, I am struggling to find a use case for this that showcases why

Re: Is D releasing too often?

On Monday, 14 May 2018 at 07:20:48 UTC, Joakim wrote: There have been 6 major releases of dmd over the last year, with ldc trying to keep pace, currently only one release behind. This is a big jump up from the previous release schedule, I see 2 major releases in 2014, 3 in 2015, and 3 in

[Issue 15869] RVO can overwrite argument

https://issues.dlang.org/show_bug.cgi?id=15869 --- Comment #13 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/0ba1f25c99bfd6e02b64b3b283540ed74e97fca5 fix Issue 15869 - RVO can overwrite argument

[Issue 15869] RVO can overwrite argument

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

Re: Is D releasing too often?

On Monday, 14 May 2018 at 07:53:40 UTC, Jonathan M Davis wrote: On Monday, May 14, 2018 07:20:48 Joakim via Digitalmars-d wrote: There have been 6 major releases of dmd over the last year, with ldc trying to keep pace, currently only one release behind. This is a big jump up from the previous

Re: Is D releasing too often?

On 05/14/2018 04:35 AM, Uknown wrote: Agree, but I think LTS releases are worth considering. A yearly release that gets only bug fixes would be useful for stability. A fair point. I have no disagreement with something like that.

Re: Is D releasing too often?

Ie, as long as there's no regression problems: If the rate of releases makes us feel like we have an embarrassment of riches, it doesn't mean that we *NEED* fewer releases. It means we need to be more appreciative that there's all those enhancements we don't have to wait for.

Re: Is D releasing too often?

On Monday, 14 May 2018 at 08:29:30 UTC, Nick Sabalausky (Abscissa) wrote: On 05/14/2018 03:20 AM, Joakim wrote: [..] Summary (That's "TL:DR" in hipster parlance): **Available** updates are always a good thing, as long as they're checked for regressions. Any issues keeping up with updates only

Re: Sealed classes - would you want them in D?

On Saturday, 12 May 2018 at 15:36:56 UTC, Walter Bright wrote: On 5/12/2018 8:18 AM, Piotr Mitana wrote: What I am trying to do is: == a.d class P { private this(); } final class C1 : P { } final class C2 : P { } test.d import a; void foo()

Re: Is D releasing too often?

On 05/14/2018 03:20 AM, Joakim wrote: There have been 6 major releases of dmd over the last year, with ldc trying to keep pace, currently only one release behind. This is a big jump up from the previous release schedule, I see 2 major releases in 2014, 3 in 2015, and 3 in 2016. This is

  1   2   >