On Sat, Oct 20, 2018 at 09:51:28AM +, Joakim via Digitalmars-d wrote:
> On Friday, 19 October 2018 at 22:19:31 UTC, H. S. Teoh wrote:
[...]
> > Haha, I feel so silly now. NDK r13b does not seem to have the
> > sysroot subdir required by the clang build command, that's why
On Fri, Oct 19, 2018 at 08:50:36PM +, Joakim via Digitalmars-d wrote:
> On Wednesday, 17 October 2018 at 21:23:21 UTC, H. S. Teoh wrote:
> > I'm trying to follow the instructions on this page:
> >
> > https://wiki.dlang.org/Build_D_for_Android
[...]
On a side
On Fri, Oct 19, 2018 at 02:41:48PM -0700, H. S. Teoh via Digitalmars-d wrote:
[...]
> In the meantime, is there a particular version of the NDK that I
> should use? Currently I have android-ndk-r13b-linux-x86_64.zip
> installed. Will it work?
[...]
Haha, I feel so silly now. NDK r13b
On Fri, Oct 19, 2018 at 02:41:48PM -0700, H. S. Teoh via Digitalmars-d wrote:
[...]
> I tried ldc-build-runtime with --ninja and it came back with a bunch of
> errors about "cortex-a8" being an unsupported target, and then
> segfaulted. So I'm going to try the "
On Fri, Oct 19, 2018 at 08:54:25PM +, Joakim via Digitalmars-d wrote:
[...]
> Also, if you're using a system-provided LDC, it may not support Android, if
> it wasn't built against our slightly tweaked llvm:
>
> https://github.com/ldc-developers/llvm
>
> In that case, use the LDC download from
On Fri, Oct 19, 2018 at 06:34:50PM +, Joakim via Digitalmars-d wrote:
> On Thursday, 18 October 2018 at 19:37:24 UTC, H. S. Teoh wrote:
[...]
> > Eventually I resorted to generating Java code from D for some fo the
> > most painful repetitive parts, and the way things a
On Thu, Oct 18, 2018 at 07:26:08PM +, MDtox via Digitalmars-d wrote:
> How to convert decimal and string to binary?
What exactly do you mean by "binary"? If you mean convert a string to a
numerical type, use std.conv.to:
import std.conv : to;
auto x = "12345";
auto i
On Thu, Oct 18, 2018 at 07:09:42PM +, Patrick Schluter via Digitalmars-d
wrote:
[...]
> I often have the impression that a lot of things are going slower than
> necessary because a mentality where the perfect is in the way of good.
That is indeed an all-too-frequent malady around these parts,
On Wed, Oct 17, 2018 at 10:13:37PM +, Stefan Koch via Digitalmars-d wrote:
> On Wednesday, 17 October 2018 at 21:55:48 UTC, H. S. Teoh wrote:
[...]
> > But nobody will be building a fusion engine out of race conditions
> > anytime in the foreseeable future. :-D
[...]
> Now
On Wed, Oct 17, 2018 at 09:29:07PM +, Stefan Koch via Digitalmars-d wrote:
> On Wednesday, 17 October 2018 at 21:12:49 UTC, Stefan Koch wrote:
> > [another person] cannot actually occupy the same space. It is
> > physically impossible.
>
> Actually, that's not quite true, If they were to try h
On Tue, Oct 16, 2018 at 05:10:38PM -0400, Nick Sabalausky (Abscissa) via
Digitalmars-d wrote:
> On 10/16/18 4:16 PM, notna wrote:
> > another interesting discussion [1]... and old/stale pull requests
> > are also discussed here now and then... not sure if this [2] is
> > known to many ppl?!
> >
>
On Fri, Oct 05, 2018 at 07:35:11PM +, AlCaponeJr via Digitalmars-d wrote:
> On Friday, 5 October 2018 at 16:11:05 UTC, H. S. Teoh wrote:
> > On Thu, Oct 04, 2018 at 11:51:02PM +, Vladimir Panteleev via
> > Digitalmars-d wrote:
[...]
> > > Yeah, painfully aware. I&#
On Fri, Oct 05, 2018 at 08:00:03PM +, Patrick Schluter via Digitalmars-d
wrote:
> On Friday, 5 October 2018 at 16:02:49 UTC, Nick Treleaven wrote:
> > On Thursday, 4 October 2018 at 06:43:02 UTC, Gopan wrote:
[...]
> > > while(1)
> > > {
> > > ...
> > > break; //otherwise return would come
On Thu, Oct 04, 2018 at 11:51:02PM +, Vladimir Panteleev via Digitalmars-d
wrote:
> On Thursday, 4 October 2018 at 19:18:15 UTC, JN wrote:
> > Seems like the issues with the forum got worse. It's hardly usable
> > today, most of the time I am being greeted by "forums are being
> > overloaded"
On Wed, Sep 26, 2018 at 02:33:27AM +, Vladimir Panteleev via Digitalmars-d
wrote:
> On Wednesday, 26 September 2018 at 01:52:31 UTC, H. S. Teoh wrote:
[...]
> > but basically, any column used in a WHERE clause is a candidate for
> > indexing.
>
> Yep, I think we
On Wed, Sep 26, 2018 at 01:07:29AM +, Vladimir Panteleev via Digitalmars-d
wrote:
[...]
> One thing possible with a traditional RDBMS that's not possible with
> SQLite is processing several simultaneous requests. The synchronous
> API translates to the synchronous nature of the entire program:
On Tue, Sep 25, 2018 at 08:41:51PM +, Vladimir Panteleev via Digitalmars-d
wrote:
> On Tuesday, 25 September 2018 at 18:26:58 UTC, CharlesM wrote:
> > Yeah it happened again today. I heard this site was made in D, maybe
> > is because the GC?
>
> No, just old server hardware and database frag
On Tue, Sep 25, 2018 at 09:00:57PM +0200, Jacob Carlborg via Digitalmars-d
wrote:
> On 2018-09-25 13:55, Jonathan M Davis wrote:
>
> > Yes. You want dmd.conf, or certain paths won't be set correctly
> > (like where to find Phobos). Personally, I'd strongly suggest
> > against having multiple copi
On Fri, Sep 21, 2018 at 07:58:56AM +, mate via Digitalmars-d wrote:
[...]
> I realize that with build instructions written in unrestricted
> language it is easier to create a dependency on something else than
> the compiler, such as the OS. Maybe they plan to solve this problem
> with appropria
On Fri, Sep 21, 2018 at 10:53:39AM +, Vladimir Panteleev via Digitalmars-d
wrote:
> On Friday, 21 September 2018 at 07:58:16 UTC, mate wrote:
> > Different sensibilities on where to put restrictions clearly lead to
> > different designs. I am not sure myself what is best.
>
> The more people
On Thu, Sep 20, 2018 at 11:25:27AM -0400, Steven Schveighoffer via
Digitalmars-d wrote:
> On 9/20/18 11:06 AM, H. S. Teoh wrote:
[...]
> > IIRC, originally the stacktrace was also built at exception
> > construction time. But it was causing a major performance hit, so
> &g
On Thu, Sep 20, 2018 at 03:45:07AM +, Vladimir Panteleev via Digitalmars-d
wrote:
[...]
> Actually it's crazier than that. The concatenation of the current
> directory plus the relative path must be < MAX_PATH (approx.).
> Meaning, if you are 50 directories deep, a relative path starting with
On Thu, Sep 20, 2018 at 08:48:13AM -0400, Steven Schveighoffer via
Digitalmars-d wrote:
[...]
> But this means you still have to build msg when throwing the
> error/exception. It's not needed until you print it, and there's no
> reason anyway to make it allocate, even with RAII. For some reason D
On Thu, Sep 13, 2018 at 06:32:54PM -0400, Nick Sabalausky (Abscissa) via
Digitalmars-d wrote:
> On 09/11/2018 09:06 AM, Steven Schveighoffer wrote:
> >
> > Then I found the true culprit was isForwardRange!R. This led me to
> > requestion my sanity, and finally realized I forgot the empty
> > func
On Sun, Sep 09, 2018 at 12:27:52AM -0600, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> IIRC, Weka has different types of assertions to differentiate between
> these two approaches - one for the cases which absolutely must not
> happen in production, and one that's purely for catching problems
On Mon, Sep 10, 2018 at 01:27:20AM +, Neia Neutuladh via Digitalmars-d
wrote:
> On Wednesday, 5 September 2018 at 05:44:38 UTC, H. S. Teoh wrote:
> > To me, this strongly suggests the following idea:
> > - add *all* dlang.org packages to our current autotester / CI
>
On Fri, Sep 07, 2018 at 04:44:05PM +, Peter Alexander via Digitalmars-d
wrote:
> I recently wrote a small program of ~600 lines of code to solve an
> optimisation puzzle. Profiling showed that GC allocations were using
> non-trivial CPU, so I decided to try and apply @nogc to remove
> allocati
On Fri, Sep 07, 2018 at 09:24:13AM -0600, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> I don't see how such a system could work very well if it's not
> automated. Simply doing it with every release of dmd means that newer
> packages won't be tested, and it would force someone to take the tim
On Fri, Sep 07, 2018 at 03:57:19PM +, Adam D. Ruppe via Digitalmars-d wrote:
> On Friday, 7 September 2018 at 15:48:39 UTC, SrMordred wrote:
> > Yes, but you don't really need this function.
>
> Whoa, when was that added?! I don't remember ctors via ufcs being
> there but indeed, it works on n
On Thu, Sep 06, 2018 at 04:32:09PM +, Everlast via Digitalmars-d wrote:
> On Thursday, 6 September 2018 at 15:28:56 UTC, Patrick Schluter wrote:
[...]
> > What annoys people is not that there are broken packages in the
> > list, but that there is no way to know beforehand if one is choosing
> >
On Thu, Sep 06, 2018 at 02:42:58PM +, Dukc via Digitalmars-d wrote:
> On Thursday, 6 September 2018 at 14:17:28 UTC, aliak wrote:
> > // D
> > auto a = "á";
> > auto b = "á";
> > auto c = "\u200B";
> > auto x = a ~ c ~ a;
> > auto y = b ~ c ~ b;
> >
> > writeln(a.length); // 2 wtf
> > writeln
On Wed, Sep 05, 2018 at 09:33:27PM +, aliak via Digitalmars-d wrote:
[...]
> The dstring is only ok because the 2 code units fit in a dchar right?
> But all the other ones are as expected right?
And dstring will be wrong once you have non-precomposed diacritics and
other composing sequences.
On Wed, Sep 05, 2018 at 04:40:19PM -0400, Nick Sabalausky (Abscissa) via
Digitalmars-d wrote:
[...]
> What we need is for DUB to quit pretending the compiler (and DUB
> itself, for that matter) isn't a dependency just like any other. I
> pointed this out years ago over at DUB's GitHub project, but
On Wed, Sep 05, 2018 at 07:35:46PM +, Meta via Digitalmars-d wrote:
[...]
> I don't disagree. I think the only sane way to use asserts as an
> optimization guide is when the program will abort if the condition
> does not hold. That, to me, makes perfect sense, since you're
> basically telling t
On Wed, Sep 05, 2018 at 07:21:51PM +, kinke via Digitalmars-d wrote:
> On Tuesday, 4 September 2018 at 04:03:19 UTC, Mike Franklin wrote:
[...]
> > Rather, we should deprecate classes, and make and expand the
> > capabilities of structs. Languages like Zig and Rust have done away
> > with clas
On Wed, Sep 05, 2018 at 03:59:06PM +, Michael via Digitalmars-d wrote:
> On Saturday, 1 September 2018 at 20:15:15 UTC, Walter Bright wrote:
> >
> > Note the "may or may not be evaluated." We've debated this here
> > before. I'm rather pleased that John agrees with me on this. I.e.
> > the op
On Wed, Sep 05, 2018 at 09:34:14AM -0600, Jonathan M Davis via Digitalmars-d
wrote:
> On Wednesday, September 5, 2018 9:28:38 AM MDT H. S. Teoh via Digitalmars-d
> wrote:
[...]
> > And that is why I think we should implement my idea of putting *all*
> > dub packages on code.dla
On Wed, Sep 05, 2018 at 09:18:24AM -0600, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> 3rd party libraries are usually the real problem if there is one. They
> need to be maintained, and if something happens that breaks them from
> one release to another, that can prevent you from upgrading u
On Wed, Sep 05, 2018 at 01:18:17AM +, James Blachly via Digitalmars-d wrote:
> On Wednesday, 5 September 2018 at 00:49:36 UTC, Everlast wrote:
> > I downloaded 3ddemo, extracted, built and I get these errors:
> >
> ...
[...]
> Are you talking about this?
>
> https://github.com/clinei/3ddemo
>
On Tue, Sep 04, 2018 at 02:00:37PM -0600, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> And while a number of us do do at least some work on D-related stuff
> that we don't care about aside from wanting to improve the D ecosystem
> for others, when the vast majority of the time being put in is
On Mon, Sep 03, 2018 at 11:39:04PM -0400, Nick Sabalausky (Abscissa) via
Digitalmars-d wrote:
> It seems pretty well established around here that:
>
> 1. Doing anything after a process has entered an unknown state is
> dangerous, and the more activity, the more danger [...]
>
> 2. For practical
On Sun, Sep 02, 2018 at 09:33:36PM -0700, H. S. Teoh wrote:
[...]
> The reason I picked memory corruption is because it's a good
> illustration of how badly things can go wrong when code that is known to
> have programming bugs continue running unchecked.
[...]
P.S. And memory corr
On Mon, Sep 03, 2018 at 03:21:00AM +, tide via Digitalmars-d wrote:
[...]
> Any graphic problems are going to stem probably more from shaders and
> interaction with the GPU than any sort of logic code.
[...]
> What he was talking about was basically that, he was saying how it
> could be used to
On Sat, Sep 01, 2018 at 01:26:01PM +, rjframe via Digitalmars-d wrote:
> On Thu, 23 Aug 2018 07:27:56 +, JN wrote:
[...]
> > (has anyone ever used contracts?).
>
> I do.
Me too. They are very useful to express intent, even if the current
implementation leaves some things to be desired.
On Fri, Aug 31, 2018 at 05:47:40PM -0600, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> The school I went to (Cal Poly, San Luis Obispo) at least tries to
> focus on the practical side of things (their motto is "learn by
> doing"), and when I went there, they even specifically had a Software
>
On Fri, Aug 31, 2018 at 04:45:57PM -0600, Jonathan M Davis via Digitalmars-d
wrote:
> On Friday, August 31, 2018 4:23:09 PM MDT Walter Bright via Digitalmars-d
> wrote:
[...]
> > That won't fix anything, because there is NO conventional wisdom in
> > software engineering for how to deal with prog
On Fri, Aug 31, 2018 at 09:40:50PM +, tide via Digitalmars-d wrote:
> On Friday, 31 August 2018 at 21:31:02 UTC, 0xEAB wrote:
[...]
> > Furthermore, how often have we cursed about games that hung up with
> > a blackscreen and didn't let us close them by any mean other than
> > logging off? If t
On Fri, Aug 31, 2018 at 08:42:38PM +, Paulo Pinto via Digitalmars-d wrote:
> On Friday, 31 August 2018 at 19:50:20 UTC, Walter Bright wrote:
> > https://news.ycombinator.com/item?id=17880722
[...]
> > And on and on. It's unbelievable. The conventional wisdom in
> > software for how to deal with
On Fri, Aug 31, 2018 at 03:13:30PM +, Chris via Digitalmars-d wrote:
> On Friday, 31 August 2018 at 14:38:36 UTC, H. S. Teoh wrote:
> > On Fri, Aug 31, 2018 at 09:37:55AM +, Chris via Digitalmars-d wrote:
> > [...]
> > > 3. moving the goal posts all the time an
On Fri, Aug 31, 2018 at 09:37:55AM +, Chris via Digitalmars-d wrote:
[...]
> 3. moving the goal posts all the time and forcing you into a new
> paradigm every 1 1/2 years (first it was "ranges", then "templates"
> and now it's "functional", wait OOP will come back one day).
[...]
Wait, what?
On Wed, Aug 29, 2018 at 07:02:42PM +, Dave Jones via Digitalmars-d wrote:
> On Wednesday, 29 August 2018 at 18:02:16 UTC, Timon Gehr wrote:
> > On 29.08.2018 19:15, H. S. Teoh wrote:
> > > On Wed, Aug 29, 2018 at 06:58:16PM +0200, Timon Gehr via
> > > Digitalmars-d w
On Wed, Aug 29, 2018 at 07:50:57PM +0200, Timon Gehr via Digitalmars-d wrote:
> On 28.08.2018 03:11, Walter Bright wrote:
> > On 8/27/2018 10:08 AM, H. S. Teoh wrote:
> > > Const in D makes sense as-is. Though, granted, its infectiousness
> > > means its scope is act
On Wed, Aug 29, 2018 at 06:58:16PM +0200, Timon Gehr via Digitalmars-d wrote:
> On 28.08.2018 19:02, H. S. Teoh wrote:
> > On Tue, Aug 28, 2018 at 08:18:57AM +, Eugene Wissner via Digitalmars-d
> > wrote:
> > [...]
> > > There are still valid use cases
On Wed, Aug 29, 2018 at 01:02:54AM +, tide via Digitalmars-d wrote:
[...]
> Point being, there is a huge difference between what you were saying,
> and what you are saying now. "This data never changes" is a much
> better guarantee and check than "this code does not modify this data".
> You use
On Tue, Aug 28, 2018 at 06:44:37PM +, aliak via Digitalmars-d wrote:
> On Tuesday, 28 August 2018 at 17:53:36 UTC, H. S. Teoh wrote:
> > On Tue, Aug 28, 2018 at 10:20:06AM -0700, Manu via
> > > D has no way to express head-const, and it turns out it's a
> >
On Tue, Aug 28, 2018 at 07:39:20PM +, tide via Digitalmars-d wrote:
> On Tuesday, 28 August 2018 at 17:02:46 UTC, H. S. Teoh wrote:
> > On Tue, Aug 28, 2018 at 08:18:57AM +, Eugene Wissner via
> > Digitalmars-d wrote: [...]
> > > There are still valid use cas
On Tue, Aug 28, 2018 at 10:20:06AM -0700, Manu via Digitalmars-d wrote:
[...]
> The reality is though, that D's const is not actually very useful, and
> C++'s const is.
Actually, I think C++ const is not very useful, because it guarantees
nothing. At the most, it's just a sanity checker to make su
On Tue, Aug 28, 2018 at 08:18:57AM +, Eugene Wissner via Digitalmars-d
wrote:
[...]
> There are still valid use cases where const should be "broken". One of
> them is mutex (another one caching). I have very little experiance in
> multi-threaded programming, but what do you think about "mutabl
On Mon, Aug 27, 2018 at 06:11:14PM -0700, Walter Bright via Digitalmars-d wrote:
> On 8/27/2018 10:08 AM, H. S. Teoh wrote:
> > Const in D makes sense as-is. Though, granted, its infectiousness means
> > its scope is actually very narrow, and as a result, we ironically
> >
On Sun, Aug 26, 2018 at 11:27:57PM -0700, Manu via Digitalmars-d wrote:
> On Sun, 26 Aug 2018 at 21:50, Walter Bright via Digitalmars-d
> wrote:
> > Going the other way, though, is even worse - what do you mean, I
> > have to write forward declarations? Why can't I pass a string
> > literal to a t
On Sun, Aug 26, 2018 at 11:12:10PM +, FeepingCreature via Digitalmars-d
wrote:
[...]
> Can I just throw in here that I like autodecoding and I think it's
> good? If you want ranges that iterate over bytes, then just use
> arrays of bytes. If you want Latin1 text, use Latin1 strings. If you
>
On Fri, Aug 24, 2018 at 09:48:33PM +, Meta via Digitalmars-d wrote:
> On Friday, 24 August 2018 at 21:43:45 UTC, Steven Schveighoffer wrote:
> > According to this comment:
> > https://github.com/dlang/phobos/pull/5291#issuecomment-360929553
> >
> > There was no way to get a deprecation to work
On Fri, Aug 24, 2018 at 09:12:40PM +, Meta via Digitalmars-d wrote:
> On Friday, 24 August 2018 at 17:12:53 UTC, H. S. Teoh wrote:
> > I got bitten by this just yesterday. Update dmd git master, update
> > vibe.d git master, now my vibe.d project doesn't compile anymore d
On Fri, Aug 24, 2018 at 04:58:12PM +, jmh530 via Digitalmars-d wrote:
> On Friday, 24 August 2018 at 16:00:10 UTC, bachmeier wrote:
> >
> > You simply can't share a D program with anyone else. It's an endless
> > cycle of compiler upgrades and figuring out how to fix code that
> > stops compil
On Thu, Aug 23, 2018 at 09:05:53PM +0300, Shachar Shemesh via Digitalmars-d
wrote:
> On 23/08/18 20:57, bachmeier wrote:
> > On Thursday, 23 August 2018 at 17:02:12 UTC, Shachar Shemesh wrote:
> >
> > > If you can, feel free to contact me off-list, and I'm fairly sure
> > > we can get the budget
On Thu, Aug 23, 2018 at 06:39:32PM +0200, ag0aep6g via Digitalmars-d wrote:
> On 08/23/2018 05:17 PM, H. S. Teoh wrote:
> > And the nice thing about D being open source is that should the
> > situation escalate to the point where the community simply cannot
> > get along with
On Thu, Aug 23, 2018 at 09:51:43PM +1200, rikki cattermole via Digitalmars-d
wrote:
> On 23/08/2018 9:45 PM, Mihails wrote:
> > On Thursday, 23 August 2018 at 09:30:45 UTC, rikki cattermole wrote:
> > > Whoever acts as a project manager would need to be given the
> > > ability to override W&A as f
On Wed, Aug 22, 2018 at 04:24:17PM -0700, Walter Bright via Digitalmars-d wrote:
> On 8/22/2018 10:28 AM, H. S. Teoh wrote:
> > I don't argue against the usefulness of the features that github
> > provides, but I'm also wary of the fact that it's basically a walled
&
On Wed, Aug 22, 2018 at 05:56:09PM +0100, Russel Winder via Digitalmars-d wrote:
> On Thu, 2018-08-16 at 16:33 -0700, H. S. Teoh via Digitalmars-d wrote:
> […]
> > I read both articles, and am quite impressed by the revolutionary
> > way of looking at concurrency. It p
On Wed, Aug 22, 2018 at 04:06:38PM +, Neia Neutuladh via Digitalmars-d
wrote:
[...]
> I'm a little paranoid about centralized services like Github. I'd
> prefer a federated service for source control / project management,
> where you could easily fork projects from my server to yours and send
On Fri, Aug 17, 2018 at 06:36:36PM +1200, rikki cattermole via Digitalmars-d
wrote:
> After reading the article I can say, it isn't any better than async
> and await for dependencies. You still need an event loop.
>
> The problem is that joining that happens at the end of that block
> needs to ru
On Fri, Aug 17, 2018 at 05:26:48PM +, jmh530 via Digitalmars-d wrote:
> On Friday, 17 August 2018 at 14:26:07 UTC, H. S. Teoh wrote:
> > [...]
> > And that is exactly why the whole implementation of @safe is
> > currently rather laughable. By blacklisting rather than
On Fri, Aug 17, 2018 at 03:39:44PM +, zabruk via Digitalmars-d wrote:
> On Friday, 17 August 2018 at 14:11:24 UTC, H. S. Teoh wrote:
> > NoScript is your friend.
> >
>
> Yes.
> But i just wonder: site creators make secret war with us (users). They
> make we harder
On Fri, Aug 17, 2018 at 01:50:32AM -0600, Jonathan M Davis via Digitalmars-d
wrote:
[...]
> Honestly, the reality of the matter is that @safe is probably always
> going to be somewhat broken, because it's implemented via blacklisting
> rather than whitelisting. Instead of @safe only allowing stuff
On Fri, Aug 17, 2018 at 11:29:46AM +, zabruk via Digitalmars-d wrote:
[...]
>
>
> Can anyone explain me the purpose of javascript on this page?
> Especialy various mouse click event handlers, those break common
> well-known handfull browser behaviour?
> I can't select text and press mouse r-c
On Thu, Aug 16, 2018 at 08:30:26PM +, John Belmonte via Digitalmars-d wrote:
[...]
> (Andrei, I hope you are reading and will check out
> https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/
> and https://vorpus.org/blog/timeouts-and-cancellation-for-human
On Fri, Jul 27, 2018 at 03:41:29AM +, Sameer Pradhan via Digitalmars-d
wrote:
[...]
> Whence came UFCS?
[...]
As far as I know, UFCS came about from a particular interpretation of
TDPL (Andrei's book). Andrei was talking about the range API, and
inserted a little note about how native arrays
On Wed, Jul 25, 2018 at 11:27:45PM +, Laeeth Isharc via Digitalmars-d wrote:
> On Tuesday, 24 July 2018 at 00:41:54 UTC, RhyS wrote:
[...]
> > I am sorry to say but to succeed as a language beyond being a small
> > or hobby language it takes: Being established already or having a
> > big name t
On Tue, Jul 24, 2018 at 01:13:16PM +, Dukc via Digitalmars-d wrote:
> On Tuesday, 24 July 2018 at 12:37:21 UTC, Cym13 wrote:
> > That argument sounds quite dangerous to me, especially since my
> > experience is on the contrary that constructor arguments are often
> > named the same as the attri
On Mon, Jul 23, 2018 at 05:32:23PM +, aliak via Digitalmars-d wrote:
> On Monday, 23 July 2018 at 16:57:20 UTC, H. S. Teoh wrote:
>
> > It's true that there's potential conflict with named arguments, but
> > IMO it's a mighty bad idea to name ctor parameters
On Mon, Jul 23, 2018 at 04:26:42PM +, Seb via Digitalmars-d wrote:
> tl;dr: the currently proposed syntax options are:
> ---
> struct S
> {
> int a = 2, b = 4, c = 6;
> }
> void foo()
> {
> bar(S({c: 10})); // Option 1
> bar(S(c: 10)); // Option 2
> bar(S{c: 10}); // Option
On Wed, Jul 18, 2018 at 07:18:52PM +, Stefan Koch via Digitalmars-d wrote:
> On Wednesday, 18 July 2018 at 18:36:37 UTC, H. S. Teoh wrote:
[...]
> > What's your current estimate on when it will be production-ready?
[...]
> I am going to give the same conservative answer I g
On Wed, Jul 18, 2018 at 06:28:30PM +, Stefan Koch via Digitalmars-d wrote:
[...]
Good to hear that progress on newCTFE is still being made.
What's your current estimate on when it will be production-ready?
T
--
Democracy: The triumph of popularity over principle. -- C.Bond
On Wed, Jul 18, 2018 at 07:08:32PM +0100, Russel Winder via Digitalmars-d wrote:
> On Wed, 2018-07-18 at 17:45 +, Johannes Pfau via Digitalmars-d
> wrote:
> > Am Wed, 18 Jul 2018 13:29:00 +0100 schrieb Russel Winder:
> […]
> > > libssl installed but libssl-dev not. I can't quite see why the
> >
On Wed, Jul 18, 2018 at 11:30:21AM -0600, Jonathan M Davis via Digitalmars-d
wrote:
> On Tuesday, July 17, 2018 21:18:12 John Colvin via Digitalmars-d wrote:
> > Just do what std.typecons.Proxy does and return float.nan for the
> > incomparable case.
>
> Since when is that legal? I thought that i
As we know, when opCmp is defined for a user type, then opEquals must
also be defined in order for == to work, even though in theory the
compiler could translate x==y into x.opCmp(y)==0.
In the past, it was argued that this was so that partial orders could be
made to work, i.e., it could be the ca
On Thu, Jul 12, 2018 at 03:28:00PM -0700, Walter Bright via Digitalmars-d wrote:
> On 7/12/2018 2:22 PM, Luís Marques wrote:
> > On Thursday, 12 July 2018 at 21:16:02 UTC, Walter Bright wrote:
> > > as Python's BDFL.
> >
> > Don't get any ideas!
>
> I have no plans to resign until they carry me o
On Mon, Jul 09, 2018 at 11:37:59PM -0700, Walter Bright via Digitalmars-d wrote:
> On 7/9/2018 6:50 PM, John Carter wrote:
> > Nothing creates flaky and unreliable systems more than allowing them
> > to wobble on past the first point where you already know that things
> > are wrong.
>
> Things got
On Thu, Jul 05, 2018 at 10:05:44PM +, John Carter via Digitalmars-d wrote:
[...]
> At work here I have emerged from a long, dark, debate on the subject
> within the team.
>
> The ultimately solution was to realize there are actually TWO
> facilities with TWO entirely different purposes that ha
On Wed, Jul 04, 2018 at 04:17:22PM -0400, Nick Sabalausky (Abscissa) via
Digitalmars-d wrote:
[...]
> Long compilation times are almost always the fault of Dub. Dub is
> pretty well-known for taking DMD's near-instant compile times and
> bloating them out to the ridiculous (by D standards) lengths
On Thu, Jul 05, 2018 at 04:55:09AM +1200, rikki cattermole via Digitalmars-d
wrote:
> On 05/07/2018 4:06 AM, jmh530 wrote:
> > On Tuesday, 3 July 2018 at 23:05:00 UTC, rikki cattermole wrote:
> > >
> > > On that note, I have a little experiment that I'd like to see
> > > done. How would the code
On Tue, Jul 03, 2018 at 02:57:07PM -0700, Walter Bright via Digitalmars-d wrote:
> A small, but important milestone has been achieved!
>
> Many thanks for the help from Sebastian Wilzbach and Rainer Schuetze.
Hopefully this eventually translates to actual improvements to the
optimizer?
T
--
I
On Fri, Jun 29, 2018 at 11:41:41PM +, SonicFreak94 via Digitalmars-d wrote:
> On Friday, 29 June 2018 at 20:57:24 UTC, Jonathan M Davis wrote:
> > [...]
> > It could be fixed, even if it's just adding a compiler switch to
> > indicate that you want it to use the GC to collect memory, because
>
On Thu, Jun 28, 2018 at 06:13:45PM +, Eugene Wissner via Digitalmars-d
wrote:
> On Thursday, 28 June 2018 at 16:24:07 UTC, H. S. Teoh wrote:
> > On Thu, Jun 28, 2018 at 04:11:57PM +, crimaniak via Digitalmars-d
> > wrote: [...]
> > > The problem is aggravated by th
On Thu, Jun 28, 2018 at 04:11:57PM +, crimaniak via Digitalmars-d wrote:
[...]
> The problem is aggravated by the fact that DUB compiles all the
> sources in one DMD launch.
Doesn't dub have an option to compile packages (i.e. subdirs)
separately? Or does that only apply to dub packages, not t
On Wed, Jun 27, 2018 at 04:00:37PM +, Mario Silva via Digitalmars-d wrote:
> Hello,
>
> Our code base has been growing steadily and it's currently at a point
> where my 16GB machine just freezes when we're compiling our code. This
> happens because DMD just consumes all my memory for a while.
On Tue, Jun 26, 2018 at 12:54:11PM -0400, Steven Schveighoffer via
Digitalmars-d wrote:
[...]
> 1. The dlang.org repository is backwards -- master generates the docs
> for the default dlang.org. I've brought this up before, still don't
> understand why we don't use stable for the latest dlang.org.
On Tue, Jun 26, 2018 at 04:17:03PM +, Timoses via Digitalmars-d wrote:
> On Tuesday, 26 June 2018 at 15:51:00 UTC, H. S. Teoh wrote:
[...]
> > Seriously, we need to start implementing versioned docs on dlang.org.
[...]
> Doesn't it already offer it?
>
> Here http
On Tue, Jun 26, 2018 at 07:25:09AM +, Mike Franklin via Digitalmars-d wrote:
[...]
> I think the documentation gets published prematurely. The new methods
> for the associative arrays should come in the next release, scheduled
> for July 1st. https://dlang.org/changelog/pending.html#require_u
When I see "DMD" and "performance" in the same sentence, my first
reaction is, "why aren't you using LDC or GDC"?
Seriously, doing performance measurements with DMD is a waste of time,
because its optimizer has been proven time and again to be suboptimal
(har!). DMD frequently produces suboptimal
1 - 100 of 4910 matches
Mail list logo
