Re: LDC 1.13.0-beta1

2018-11-03 Thread Johan Engelen via Digitalmars-d-announce
On Friday, 2 November 2018 at 21:04:13 UTC, kinke wrote: Glad to announce the first beta for LDC 1.13: Note how fast Martin produced this beta release after the DMD 2.083 release. Thanks to all contributors! The main contributor by far is you Martin, thank _you_! -Johan

Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-11-03 Thread Walter Bright via Digitalmars-d-announce
On 11/2/2018 5:44 PM, Laeeth Isharc wrote: When one encounters a new idea that's unfamiliar sometimes it's easy to think that because it's unfamiliar it must be unsound. That can be a mistake.  It might be better to suspend judgement for a while and keep an open mind. So true. My ideas on how

Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-11-03 Thread Stanislav Blinov via Digitalmars-d-announce
On Saturday, 3 November 2018 at 20:38:29 UTC, unprotected-entity wrote: As has been pointed out several times before, this is a contrived example. Allow a simple transformation: ``` module test; struct S { private uint a; void setA(uint n) { // damn implicit conversions!

Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-11-03 Thread unprotected-entity via Digitalmars-d-announce
On Saturday, 3 November 2018 at 06:57:50 UTC, Neia Neutuladh wrote: We object because the people complaining can't point at a use case that seems reasonable. If you provided real-world examples, we'd consider them. -- module test; struct S { private uint a; void setA(uint n)

Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-11-03 Thread unprotected-entity via Digitalmars-d-announce
On Saturday, 3 November 2018 at 06:57:50 UTC, Neia Neutuladh wrote: On Sat, 03 Nov 2018 04:50:52 +, unprotected-entity wrote: (q1) Why is it, that people who use D, object *so much* to the idea of allowing (at the choice of the programmer) for a type to have it's own private state *within*

Re: LDC 1.13.0-beta1

2018-11-03 Thread Bastiaan Veelo via Digitalmars-d-announce
On Friday, 2 November 2018 at 21:04:13 UTC, kinke wrote: Glad to announce the first beta for LDC 1.13: * Based on D 2.083.0. * The Windows packages are now fully self-sufficient, i.e., a Visual Studio/C++ Build Tools installation isn't required anymore. * Substantial debug info improvements f

Re: LDC 1.13.0-beta1

2018-11-03 Thread drug via Digitalmars-d-announce
On 03.11.2018 19:33, kinke wrote: I figured it'd be for a lot of Windows users. Why not explicitly express your gratitude with a little 'thank you' then? After all, that little bullet point in the release notes easily took some 40 hours of my spare time, and some appreciation can work wonders

Re: LDC 1.13.0-beta1

2018-11-03 Thread kinke via Digitalmars-d-announce
On Saturday, 3 November 2018 at 00:42:46 UTC, bachmeier wrote: On Friday, 2 November 2018 at 21:04:13 UTC, kinke wrote: * The Windows packages are now fully self-sufficient, i.e., a Visual Studio/C++ Build Tools installation isn't required anymore. That's a very big deal for me. It will be re

Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-11-03 Thread Neia Neutuladh via Digitalmars-d-announce
On Sat, 03 Nov 2018 11:24:06 +, FooledDonor wrote: > And if the validity of a person's reasoning is a function of his way of > expressing them, well ... do not pose to software engineers at least If you want other people to do work for you, you need to convince them to do it. This is an open

Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-11-03 Thread FooledDonor via Digitalmars-d-announce
On Saturday, 3 November 2018 at 06:57:50 UTC, Neia Neutuladh wrote: On Sat, 03 Nov 2018 04:50:52 +, unprotected-entity wrote: (q1) Why is it, that people who use D, object *so much* to the idea of allowing (at the choice of the programmer) for a type to have it's own private state *within*

Re: Wed Oct 17 - Avoiding Code Smells by Walter Bright

2018-11-03 Thread Neia Neutuladh via Digitalmars-d-announce
On Sat, 03 Nov 2018 04:50:52 +, unprotected-entity wrote: > (q1) Why is it, that people who use D, object *so much* to the idea of > allowing (at the choice of the programmer) for a type to have it's own > private state *within* a module (so that its private state is respected > by other code a