Re: .sort vs sort(): std.algorithm not up to the task?

On Thursday, 8 June 2017 at 04:15:12 UTC, Stanislav Blinov wrote: Earns you nothing? How about not performing an allocation and copy? Seen through the eyes of a complete beginner, this means absolutely nothing. Those are the eyes I am using as I'm reading a book and simply following the

[Issue 17479] New: Public constructor for std.process.Pid

https://issues.dlang.org/show_bug.cgi?id=17479 Issue ID: 17479 Summary: Public constructor for std.process.Pid Product: D Version: D2 Hardware: x86_64 OS: All Status: NEW Severity: enhancement

[Issue 17479] Public constructor for std.process.Pid

https://issues.dlang.org/show_bug.cgi?id=17479 Chris Wright changed: What|Removed |Added Priority|P1 |P3 --

Re: Compile-Time Sort in D

On Tuesday, 6 June 2017 at 01:08:45 UTC, Mike Parker wrote: On Monday, 5 June 2017 at 17:54:05 UTC, Jon Degenhardt wrote: Very nice post! Thanks! If it gets half as many page views as yours did, I'll be happy. Yours is the most-viewed post on the blog -- over 1000 views more than #2 (my

Re: Concept proposal: Safely catching error

On Monday, 5 June 2017 at 13:13:01 UTC, ketmar wrote: this still nullifies the sense of Error/Exception differences. not all errors are recoverable, even in @safe code. ... using wrappers and carefully checking preconditions looks better to me. after all, if programmer failed to check some

Re: DIP 1003 (Remove body as a Keyword) Accepted!

On Friday, 2 June 2017 at 14:17:10 UTC, Mike Parker wrote: Congratulations are in order for Jared Hanson. Walter and Andrei have approved his proposal to remove body as a keyword. I've added a summary of their decision to the end of the DIP for anyone who cares to read it. In short: * body

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Vladimir Panteleev changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #5 from Vladimir Panteleev --- (In reply to Mathias Lang from comment #4) > So you can implicitly capture TLS variables and use them from other thread ? > Doesn't that completely defeat the purpose of thread

[Issue 17475] [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 Vladimir Panteleev changed: What|Removed |Added Status|NEW |RESOLVED

The reason for SIGSEGV function pointer problem

OK, so I have narrowed down my SIGSEGV problem to having no real idea how to do C function pointers in D code. So I have a callback function that will be called from C library code. It currently has signature: extern(C) int checkFrontend(void* _arguments, dvb_v5_fe_parms*

[Issue 17475] [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 --- Comment #2 from b2.t...@gmx.com --- (In reply to Vladimir Panteleev from comment #1) > You have a mismatching libphobos again. > > In the future, please test with a D build tool that removes the possibility > of user errors, such as Digger. Are

[Issue 17475] [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 --- Comment #3 from Vladimir Panteleev --- (In reply to b2.temp from comment #2) > Are you sure ? Yes: ~/work/Digger/work/repo » git checkout 13da2d4e97bf15c7049138012bde243a221be117 ; git submodule update ; git submodule

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #6 from Andrej Mitrovic --- > In main, you set the TLS instance of path corresponding to the main thread to > "foobar". The "parallel" loop body will use the current thread's TLS > instance, but because the

Re: DIP 1007--"future symbol"--Formal Review

On Wednesday, 7 June 2017 at 14:42:24 UTC, Mike Parker wrote: I'll be revising it a bit in the near future based on the lessons I've learned so far to clarify the process, but I want to keep this thread focused on feedback. Thanks! https://github.com/dlang/DIPs/blob/master/README.md

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Mathias Lang changed: What|Removed |Added CC|

Re: The reason for SIGSEGV function pointer problem

On Wednesday, 7 June 2017 at 16:50:26 UTC, Russel Winder wrote: In the constructor of an object to abstract the result of a call to the C library code, the parameter is: check_frontend_t* cf You should remove the pointer here... /Paolo

Re: Concept proposal: Safely catching error

On Monday, 5 June 2017 at 12:51:16 UTC, ag0aep6g wrote: On 06/05/2017 11:50 AM, Olivier FAURE wrote: In other words, @safe functions would be allowed to catch Error after try blocks if the block only mutates data declared inside of it; the code would look like: import vibe.d; //

Re: Concept proposal: Safely catching error

On Monday, 5 June 2017 at 12:59:11 UTC, Moritz Maxeiner wrote: On Monday, 5 June 2017 at 12:01:35 UTC, Olivier FAURE wrote: Another problem is that non-gc memory allocated in the try block would be irreversibly leaked when an Error is thrown (though now that I think about it, that would

Re: Ali's slides from his C++Now talk

On Wednesday, 7 June 2017 at 07:53:25 UTC, Bastiaan Veelo wrote: On Wednesday, 24 May 2017 at 02:42:47 UTC, Jack Stouffer wrote: On Wednesday, 24 May 2017 at 00:05:54 UTC, Ali Çehreli wrote: ... Any videos up? The video is up: https://www.youtube.com/watch?v=vYEKEIpM2zo Ali, what was the

Re: Concept proposal: Safely catching error

On Wednesday, 7 June 2017 at 15:35:56 UTC, Olivier FAURE wrote: On Monday, 5 June 2017 at 12:59:11 UTC, Moritz Maxeiner wrote: Anyway, I don't think this would happen. Most forms of memory allocations are impure, Not how pure is currently defined in D, see the referred spec; allocating

Re: Ali's slides from his C++Now talk

On 06/07/2017 08:58 AM, Steven Schveighoffer wrote: >> The video is up: https://www.youtube.com/watch?v=vYEKEIpM2zo > > Ali, what was the fiber question you couldn't answer? > > -Steve I wouldn't remember the question even when watching it myself, except for one word that I luckily repeated:

fluent-asserts 0.5.0 released

Hi, I just released a new version of fluent-asserts: https://github.com/gedaiu/fluent-asserts Since the previous announce, I improved the error messages and I added a new function `.because()` that allows you to add custom messages. If you are interested in writing better asserts in your

Re: Why does phobos have collisions?

07.06.2017 17:57, Ivan Kazmenko пишет: On Wednesday, 7 June 2017 at 10:01:30 UTC, Mike B Johnson wrote: Error: template std.algorithm.mutation.strip cannot deduce function from argument types !()(string), candidates are: src\phobos\std\algorithm\mutation.d(2280):

Re: Concept proposal: Safely catching error

On Monday, 5 June 2017 at 14:05:27 UTC, Steven Schveighoffer wrote: I don't think this will work. Only throwing Error makes a function nothrow. A nothrow function may not properly clean up the stack while unwinding. Not because the stack unwinding code skips over it, but because the compiler

[Issue 17469] View source code

https://issues.dlang.org/show_bug.cgi?id=17469 --- Comment #3 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/dlang.org https://github.com/dlang/dlang.org/commit/d02045747db953d021649f222e07c71c0705dbb0 Fix Issue 17469 - View source code for object.d is

Re: Can assumeSafeAppend() grab more and more capacity?

On Wednesday, June 07, 2017 07:43:06 ag0aep6g via Digitalmars-d-learn wrote: > You understand the spec to say that because `foo.capacity` is 15 at one > point, you should then be able to put 15 elements into `foo` without > relocation. And what `bar` does in the meantime shouldn't matter. > > I

[Issue 9275] [GC] removeRoot hits assert(0) instead of being a no-op (as documented)

https://issues.dlang.org/show_bug.cgi?id=9275 --- Comment #4 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/druntime https://github.com/dlang/druntime/commit/a1fb3915f562428741324ac5b319d9316fb57231 Fix issue 9275: Add test for removeRoot Issue 9275

[Issue 9275] [GC] removeRoot hits assert(0) instead of being a no-op (as documented)

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

Re: [Solved] Confusing error message

On Wednesday, 7 June 2017 at 14:58:26 UTC, drug wrote: 07.06.2017 16:27, Wulfklaue пишет: Some of the dmd error messages need some tweaking. import std.datetime; auto t = Clock.currStdTime; writeln(to!string(t)); Result in: Error: template core.time.to cannot deduce function from

Re: rawRead using a struct with variable leght

On Monday, 5 June 2017 at 16:30:53 UTC, Era Scarecrow wrote: On Monday, 5 June 2017 at 16:04:28 UTC, ade90036 wrote: Unfortunately the struct doesn't know at compile time what the size of the constant_pool array, or at-least was not able to specify it dynamically. It also won't know ahead

sqlite3 vs. sqlite-d

Hi guys I made a small video. Mature and heavily optimized C library vs. young D upstart. See for yourself how it turns out. https://www.youtube.com/watch?v=mOeVftcVsvI Cheers, Stefan

Re: The reason for SIGSEGV function pointer problem

On 06/07/2017 06:50 PM, Russel Winder via Digitalmars-d-learn wrote: So why isn't a thing of type check_frontend_t* AFAIK, you would usually translate: typedef int (check_frontend_t*)(void *args, struct dvb_v5_fe_parms *parms); into: alias check_frontend_t = extern(C) int function (void*

Re: [Solved] Confusing error message

07.06.2017 21:07, bachmeier пишет: On Wednesday, 7 June 2017 at 14:58:26 UTC, drug wrote: For me it's a good message. Messages like this were an annoyance when I started out. If you don't import std.stdio, you get the error message Error: 'writeln' is not defined, perhaps you need to

Re: Mutiple AliasSeq as input to template

On Thursday, 25 May 2017 at 17:56:12 UTC, jmh530 wrote: On Thursday, 25 May 2017 at 16:36:45 UTC, jmh530 wrote: [snip] I haven't played around with it fully, but it seems like the following resolves my issue in a sort of manual way: template Process1(A, B) { static if (!isIndex!B)

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #7 from Mathias Lang --- When a thread runs I would expect the following (simplified) course of action: - Initialize the TLS data - Do the writeln - Exit Given the original code, I would then expect the

Re: rawRead using a struct with variable leght

On Wed, Jun 07, 2017 at 06:24:22PM +, ade90036 via Digitalmars-d-learn wrote: > On Monday, 5 June 2017 at 16:30:53 UTC, Era Scarecrow wrote: > > On Monday, 5 June 2017 at 16:04:28 UTC, ade90036 wrote: > > > > > Unfortunately the struct doesn't know at compile time what the > > > size of the

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #8 from Vladimir Panteleev --- (In reply to Mathias Lang from comment #7) > How can > "foobar" be printed twice if it's only set for one thread ? Because both times "foobar" is written are done from the same

Re: import statement placement

On Wed, Jun 07, 2017 at 01:17:39PM +, Nicholas Wilson via Digitalmars-d-learn wrote: > On Wednesday, 7 June 2017 at 12:39:07 UTC, Russel Winder wrote: > > Are there any idiom rules as to where to put import statements in D? > > > > In Python they can go anywhere but PEP-8 suggests they

Re: The reason for SIGSEGV function pointer problem

On 06/07/2017 06:50 PM, Russel Winder via Digitalmars-d-learn wrote: So why isn't a thing of type check_frontend_t*? It's a thing of type `check_frontend_t`, which is a function pointer already. When you add an asterisk, you get a pointer to a function pointer.

Re: Dynamic binding to the Mono runtime API

On 6/4/17 04:15, Jakub Szewczyk wrote: On Sunday, 4 June 2017 at 09:43:23 UTC, Adam Wilson wrote: On 6/4/17 01:18, Jakub Szewczyk wrote: This is an interface to the Mono libraries, D/CLI would [...] My interest is less in code ports than bindings to the actual code. My experience with code

Re: Can assumeSafeAppend() grab more and more capacity?

On Wednesday, 7 June 2017 at 05:43:06 UTC, ag0aep6g wrote: [snip] It seems to me this is a topic worthy of a more in-depth article. If only I felt up to that. :p When you create a slice 'a' in D (with the current GC and druntime, at least), what happens behind the scenes is the allocator

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 Tomer Filiba (weka) changed: What|Removed |Added Keywords||industry

Re: Ali's slides from his C++Now talk

On Wednesday, 24 May 2017 at 02:42:47 UTC, Jack Stouffer wrote: On Wednesday, 24 May 2017 at 00:05:54 UTC, Ali Çehreli wrote: ... Any videos up? The video is up: https://www.youtube.com/watch?v=vYEKEIpM2zo

Re: sqlite3 vs. sqlite-d

On Wednesday, 7 June 2017 at 19:10:26 UTC, Ozan wrote: On Wednesday, 7 June 2017 at 17:51:30 UTC, Stefan Koch wrote: Hi guys I made a small video. Mature and heavily optimized C library vs. young D upstart. See for yourself how it turns out. https://www.youtube.com/watch?v=mOeVftcVsvI

Re: rawRead using a struct with variable leght

On Wednesday, 7 June 2017 at 18:31:41 UTC, H. S. Teoh wrote: "Structs" with variable size fields have no direct equivalent in D's type system, so you'll probably have a hard time mapping this directly. What you *could* do, though, is to load the data into a ubyte[] buffer, then create a

Black Duck: DMD license corrected

Hi, Black duck is a software and a service for enterprises to evaluate the usage of OSS in their products to avoid legal risks. DMD license type is now corrected. There is also a non commercial public available service of Black duck called OpenHub. Here is DMD still listed with the old

Re: sqlite3 vs. sqlite-d

On Wednesday, 7 June 2017 at 17:51:30 UTC, Stefan Koch wrote: Hi guys I made a small video. Mature and heavily optimized C library vs. young D upstart. See for yourself how it turns out. https://www.youtube.com/watch?v=mOeVftcVsvI Cheers, Stefan It should be noted that the benchmark isn't

Re: sqlite3 vs. sqlite-d

On Wed, Jun 07, 2017 at 08:40:12PM +, Stefan Koch via Digitalmars-d wrote: > [...] Also sqlite-d is inefficient in quite a few places and is > slowed down by auto-decoding as I discovered just now. *dreams of a day when we can finally be free of auto-decoding...* T -- If you think you

Re: [Solved] Confusing error message

On Wednesday, 7 June 2017 at 19:02:59 UTC, drug wrote: How do compiler know that you want use `std.conv.to` instead of _already imported_ `core.time.to`? In general it's impossible. There is no way for compiler to guess that you want some other symbol from out there. What if you've imported

Re: Concept proposal: Safely catching error

On 06/07/2017 05:19 PM, Olivier FAURE wrote: How does `@trusted` fit into this? The premise is that there's a bug somewhere. You can't assume that the bug is in a `@system` function. It can just as well be in a `@trusted` one. And then `@safe` and `pure` mean nothing. I think I mistyped

Re: vibe.d on Web Framework Benchmarks

On Wednesday, 7 June 2017 at 14:56:56 UTC, Ozan wrote: On Wednesday, 7 June 2017 at 09:44:55 UTC, Ali Çehreli wrote: Is there an issue with the tests? Surprised that vibe.d is not higher in the rating... https://www.techempower.com/benchmarks/#section=data-r14=ph=fortune Ali Same for me.

Re: Can assumeSafeAppend() grab more and more capacity?

On 6/7/17 3:56 AM, Biotronic wrote: On Wednesday, 7 June 2017 at 05:43:06 UTC, ag0aep6g wrote: [snip] It seems to me this is a topic worthy of a more in-depth article. If only I felt up to that. :p Your understanding and explanation is excellent actually! When you create a slice 'a' in D

Re: sqlite3 vs. sqlite-d

On Wednesday, 7 June 2017 at 17:51:30 UTC, Stefan Koch wrote: Hi guys I made a small video. Mature and heavily optimized C library vs. young D upstart. See for yourself how it turns out. https://www.youtube.com/watch?v=mOeVftcVsvI Cheers, Stefan Great. I like it (not the color of the

Re: [Solved] Confusing error message

07.06.2017 22:40, bachmeier пишет: On Wednesday, 7 June 2017 at 19:02:59 UTC, drug wrote: How do compiler know that you want use `std.conv.to` instead of _already imported_ `core.time.to`? In general it's impossible. There is no way for compiler to guess that you want some other symbol from

Re: sqlite3 vs. sqlite-d

On Wednesday, 7 June 2017 at 20:12:22 UTC, cym13 wrote: It should be noted that the benchmark isn't fair, it favours the sqlite3 implementation as parsing and preparing the statement isn't measured. And yes, it's still faster which is cool ^^ Yes the benchmark is biased slightly in favor

Re: Concept proposal: Safely catching error

On 06/07/2017 09:45 PM, ag0aep6g wrote: When no @trusted code is involved, then catching an out-of-bounds error from a @safe function is safe. No additional rules are needed. Assuming no compiler bugs, a @safe function simply cannot corrupt memory without calling @trusted code. Thinking a

Re: Compile-Time Sort in D

On Tuesday, 6 June 2017 at 01:08:45 UTC, Mike Parker wrote: On Monday, 5 June 2017 at 17:54:05 UTC, Jon Degenhardt wrote: Very nice post! Thanks! If it gets half as many page views as yours did, I'll be happy. Yours is the most-viewed post on the blog -- over 1000 views more than #2 (my

DIP 1007--"future symbol"--Formal Review

The first stage of the formal review for DIP 1007 [1], "'future symbol' Compiler Concept", is now underway. From now until 11:59 PM ET on June 21 (3:59 AM GMT on June 22), the community has the opportunity to provide last-minute feedback. If you missed the preliminary review [2], this is your

DIP 1007--"future symbol"--Formal Review Has Begun

The the formal review for DIP 1007, "'future symbol' Compiler Concept", is now underway. Please provide all feedback in the review thread: http://forum.dlang.org/post/ldjlsobcdevxiitqy...@forum.dlang.org

My DMD ~master build gives linker error and IDK why

This is my script: HOST_DMD=dmd MODEL=64 cd dmd make -fposix.mak MODEL=64 clean make -fposix.mak ENABLE_RELEASE=1 MODEL=64 DMD=../dmd/src/dmd -j 5 cd ../druntime make -fposix.mak MODEL=64 clean make -fposix.mak MODEL=64 DMD=../dmd/src/dmd -j 5 cd ../phobos make -fposix.mak MODEL=64 clean

Re: My DMD ~master build gives linker error and IDK why

On Wednesday, 7 June 2017 at 09:50:41 UTC, Basile B. wrote: bla bla bla Actually it's this code: void main(string[] args) { import std.stdio; import std.compiler; writeln(vendor); } that gives the error. I suspect a regression.

[Issue 17474] non-property being treated as a property

https://issues.dlang.org/show_bug.cgi?id=17474 ZombineDev changed: What|Removed |Added CC|

Why does phobos have collisions?

Error: template std.algorithm.mutation.strip cannot deduce function from argument types !()(string), candidates are: src\phobos\std\algorithm\mutation.d(2280): std.algorithm.mutation.strip(Range, E)(Range range, E element) if (isBidirectionalRange!Range && is(typeof(range.front ==

Re: My DMD ~master build gives linker error and IDK why

On Wednesday, 7 June 2017 at 09:55:24 UTC, Basile B. wrote: On Wednesday, 7 June 2017 at 09:50:41 UTC, Basile B. wrote: bla bla bla Actually it's this code: void main(string[] args) { import std.stdio; import std.compiler; writeln(vendor); } that gives the error. I suspect a

better string

Why not alias string so that one can easily switch from the old string or wstring, etc? e.g., rename string internally to sstring or whatever. then globally define alias string = sstring; Which can be over realiased to wstring to affect the whole program alias string = wstring; Or use a

vibe.d on Web Framework Benchmarks

Is there an issue with the tests? Surprised that vibe.d is not higher in the rating... https://www.techempower.com/benchmarks/#section=data-r14=ph=fortune Ali

[Issue 17475] New: [REG2.075] linker error on specific code

https://issues.dlang.org/show_bug.cgi?id=17475 Issue ID: 17475 Summary: [REG2.075] linker error on specific code Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: regression

Re: better string

On Wednesday, 7 June 2017 at 10:58:06 UTC, Mike B Johnson wrote: Why not alias string so that one can easily switch from the old string or wstring, etc? [...] I'd suggest to avoid utf16 wherever possible. why? http://utf8everywhere.org/

Re: better string

On Wednesday, 7 June 2017 at 10:58:06 UTC, Mike B Johnson wrote: Why not alias string so that one can easily switch from the old string or wstring, etc? e.g., rename string internally to sstring or whatever. then globally define alias string = sstring; Which can be over realiased to wstring

Re: vibe.d on Web Framework Benchmarks

Ozan wrote: On Wednesday, 7 June 2017 at 09:44:55 UTC, Ali Çehreli wrote: Is there an issue with the tests? Surprised that vibe.d is not higher in the rating... https://www.techempower.com/benchmarks/#section=data-r14=ph=fortune Same for me. I used a lot of Java (Jetty, Tomcat) and Groovy

[Issue 17477] DMD error message for delegate with wrong attributes is very confusing

https://issues.dlang.org/show_bug.cgi?id=17477 Eyal changed: What|Removed |Added Keywords||diagnostic --

[Issue 17477] New: DMD error message for delegate with wrong attributes is very confusing

https://issues.dlang.org/show_bug.cgi?id=17477 Issue ID: 17477 Summary: DMD error message for delegate with wrong attributes is very confusing Product: D Version: D2 Hardware: x86_64 OS: Linux

Re: Black Duck: DMD license corrected

Thanks for taking care of this.

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 ag0ae...@gmail.com changed: What|Removed |Added Keywords||rejects-valid CC|

Re: Compile-Time Sort in D

On Wednesday, 7 June 2017 at 21:47:58 UTC, John Carter wrote: On Monday, 5 June 2017 at 14:23:34 UTC, Mike Parker wrote: https://dlang.org/blog/2017/06/05/compile-time-sort-in-d/ Seems like you have inspired people... http://blog.zdsmith.com/posts/compiletime-sort-in-nim.html We should

[Issue 17473] foreach on delegates incorrectly rejected

https://issues.dlang.org/show_bug.cgi?id=17473 --- Comment #5 from Eyal --- (In reply to Vladimir Panteleev from comment #4) > Adding `ref` to `char a` fixes compilation, but it's still weird that > `ref`'s presence is inconsistently needed. It also changes the meaning of the

Re: [Solved] Confusing error message

On Wed, Jun 07, 2017 at 11:16:14PM +0300, drug via Digitalmars-d-learn wrote: > 07.06.2017 22:40, bachmeier пишет: [...] > > In any event, I made a second suggestion that would always work. If > > it can't find a match, it asks if you're missing an import > > statement, as a way to provide the new

Re: vibe.d on Web Framework Benchmarks

On Thu, Jun 08, 2017 at 12:18:21AM +0300, ketmar via Digitalmars-d wrote: > Ozan wrote: > > > On Wednesday, 7 June 2017 at 09:44:55 UTC, Ali Çehreli wrote: > > > Is there an issue with the tests? Surprised that vibe.d is not > > > higher in the rating... > > > > > >

Re: better string

On 06/07/2017 12:58 PM, Mike B Johnson wrote: Why not alias string so that one can easily switch from the old string or wstring, etc? e.g., rename string internally to sstring or whatever. then globally define alias string = sstring; Which can be over realiased to wstring to affect the

Re: Compile-Time Sort in D

On Monday, 5 June 2017 at 14:23:34 UTC, Mike Parker wrote: https://dlang.org/blog/2017/06/05/compile-time-sort-in-d/ Seems like you have inspired people... http://blog.zdsmith.com/posts/compiletime-sort-in-nim.html

Re: Ali's slides from his C++Now talk

On 06/07/2017 09:56 AM, Ali Çehreli wrote: On 06/07/2017 08:58 AM, Steven Schveighoffer wrote: The video is up: https://www.youtube.com/watch?v=vYEKEIpM2zo Ali, what was the fiber question you couldn't answer? -Steve I wouldn't remember the question even when watching it myself, except

Re: DIP 1007--"future symbol"--Formal Review

On 6/7/2017 3:36 AM, Mike Parker wrote: The first stage of the formal review for DIP 1007 [1], "'future symbol' Compiler Concept", is now underway. From now until 11:59 PM ET on June 21 (3:59 AM GMT on June 22), the community has the opportunity to provide last-minute feedback. If you missed

Re: better string

On Wednesday, 7 June 2017 at 21:32:25 UTC, ag0aep6g wrote: On 06/07/2017 12:58 PM, Mike B Johnson wrote: Why not alias string so that one can easily switch from the old string or wstring, etc? e.g., rename string internally to sstring or whatever. then globally define alias string =

[Issue 17476] New: Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Issue ID: 17476 Summary: Static fields don't seem to be reliably initialized when using parallel() Product: D Version: D2 Hardware: x86_64 OS: Linux

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 --- Comment #1 from anonymous4 --- In the first thread it will be "foobar", in other threads it will be "/some/string/initializer", the exact sequence may depend on how parallel selects threads. --

Re: DMD is now part of the doc pages on dlang.org

On Wednesday, 7 June 2017 at 00:17:30 UTC, Walter Bright wrote: On 6/6/2017 3:13 PM, Seb wrote: Hi all, I have excellent news on the front of DMD becoming a library. DMD on dlang.org Since today DMD's documentation is browseable online on the released docs: Ddoc:

Re: DMD is now part of the doc pages on dlang.org

On 07/06/2017 12:30 PM, Wulfklaue wrote: On Wednesday, 7 June 2017 at 00:17:30 UTC, Walter Bright wrote: On 6/6/2017 3:13 PM, Seb wrote: Hi all, I have excellent news on the front of DMD becoming a library. DMD on dlang.org Since today DMD's documentation is browseable

[Issue 17476] Static fields don't seem to be reliably initialized when using parallel()

https://issues.dlang.org/show_bug.cgi?id=17476 Stefan Koch changed: What|Removed |Added CC||uplink.co...@gmail.com

Re: DMD is now part of the doc pages on dlang.org

On Wednesday, 7 June 2017 at 11:37:21 UTC, rikki cattermole wrote: std.datetime has been very recently broken up, it hasn't been in a release as of yet. Give it a release, it'll be fixed. Ok, thanks. Just my bad luck for trying out the one part that just got broken up. *haha*

import statement placement

Are there any idiom rules as to where to put import statements in D? In Python they can go anywhere but PEP-8 suggests they should all go at the top of a file, just after the module documentation string. -- Russel. = Dr

Re: better string

On Wednesday, 7 June 2017 at 23:57:44 UTC, Mike B Johnson wrote: Or will simply setting "alias string = wstring;" at the top of my program end up having the entire program, regardless of what it is, use wstring's instead of strings? It doesn't work that way and it can't work that way: you'd

Re: better string

On Thursday, 8 June 2017 at 00:59:06 UTC, Stanislav Blinov wrote: On Wednesday, 7 June 2017 at 23:57:44 UTC, Mike B Johnson wrote: Or will simply setting "alias string = wstring;" at the top of my program end up having the entire program, regardless of what it is, use wstring's instead of

Re: .sort vs sort(): std.algorithm not up to the task?

On Thursday, 8 June 2017 at 01:57:47 UTC, Andrew Edwards wrote: If I hand you a chihuahua for grooming, why am I getting back a pit bull? I simply want a groomed chihuahua. Why do I need to consult a wizard to get back a groomed chihuahua? Because is like a poodle and unless you get your hair

Re: .sort vs sort(): std.algorithm not up to the task?

On Thursday, 8 June 2017 at 02:07:07 UTC, Mike B Johnson wrote: On Thursday, 8 June 2017 at 01:57:47 UTC, Andrew Edwards wrote: If I hand you a chihuahua for grooming, why am I getting back a pit bull? I simply want a groomed chihuahua. Why do I need to consult a wizard to get back a groomed

Re: .sort vs sort(): std.algorithm not up to the task?

On Thursday, 8 June 2017 at 02:19:15 UTC, Andrew Edwards wrote: Pretty funny. But seriously, this is something that just work. There is now to layers of indirection to achieve what I used to do quite naturally in the language. *should just work

[Issue 15692] Allow struct member initializer everywhere

https://issues.dlang.org/show_bug.cgi?id=15692 greensunn...@gmail.com changed: What|Removed |Added CC||greensunn...@gmail.com --- Comment

[Issue 17478] New: Socket.select return a write status change, but no connection is established.

https://issues.dlang.org/show_bug.cgi?id=17478 Issue ID: 17478 Summary: Socket.select return a write status change, but no connection is established. Product: D Version: D2 Hardware: x86_64 OS: Other

Re: better string

On Wednesday, June 07, 2017 10:58:06 Mike B Johnson via Digitalmars-d wrote: > Why not alias string so that one can easily switch from the old > string or wstring, etc? > > e.g., rename string internally to sstring or whatever. > > then globally define > > alias string = sstring; > > Which can be

Re: Compile-Time Sort in D

On Wednesday, 7 June 2017 at 20:59:50 UTC, Joakim wrote: On Tuesday, 6 June 2017 at 01:08:45 UTC, Mike Parker wrote: On Monday, 5 June 2017 at 17:54:05 UTC, Jon Degenhardt wrote: Very nice post! Thanks! If it gets half as many page views as yours did, I'll be happy. Yours is the

Re: [Solved] Confusing error message

On Wednesday, 7 June 2017 at 21:13:37 UTC, H. S. Teoh wrote: On Wed, Jun 07, 2017 at 11:16:14PM +0300, drug via Digitalmars-d-learn wrote: 07.06.2017 22:40, bachmeier пишет: [...] > In any event, I made a second suggestion that would always > work. If it can't find a match, it asks if you're

  1   2   >