Re: D for microservices

On Thursday, 8 March 2018 at 07:20:53 UTC, Radu wrote: This guys says that vide.d works https://forum.dlang.org/thread/gikoeutmdyvolfshp...@forum.dlang.org Yes, it's pretty straightforward: 1. Build on Ubuntu, or some other dist 2. Statically link the whole binary with LDC, then you don't

Re: DWT API Documentation now on dpldocs.info

On Thursday, 8 March 2018 at 01:21:44 UTC, Adam D. Ruppe wrote: As some of you might know, DWT is a D port of Java's SWT. It is as thus nearly identical and you can use Java's documentation with very little effort - copy/paste of Java examples almost just work as D too. [...] Thank you,

Re: mysql-native v2.1.0

On 03/08/2018 02:14 AM, Bauss wrote: By any chance, are you ever storing a Connection or a ResultRange anywhere? I don't mean as a function-local variable or a a function parameter: I mean like as a class/struct member or as a global? (Well, not that D really has true globals, but a "global"

Re: D for microservices

On Thursday, 8 March 2018 at 06:49:07 UTC, Andrew Benton wrote: On Monday, 5 March 2018 at 17:58:25 UTC, Joakim wrote: [...] I took a shot at dockerizing dub-registry with the alpine build using multistage builds. I got ldc installed and dub built. Unfortunately when I tried to build

Re: Lobst.rs now has a "D" tag

On Wednesday, 7 March 2018 at 16:34:31 UTC, Pradeep Gowda wrote: https://lobste.rs/t/d Please do not forget to tag your D related submissions with the "D" tag. Can someone invite me at baussproje...@gmail.com

Re: mysql-native v2.1.0

On Thursday, 8 March 2018 at 07:03:15 UTC, Nick Sabalausky (Abscissa) wrote: On 03/07/2018 04:53 PM, bauss wrote: I can't seem to reproduce it now, but I'll keep an eye for it and see if it still happens, but I think the problem is when you return the connection from a function. I had

Re: mysql-native v2.1.0

On 03/07/2018 04:53 PM, bauss wrote: I can't seem to reproduce it now, but I'll keep an eye for it and see if it still happens, but I think the problem is when you return the connection from a function. I had similar issues returning a raw connection created. By any chance, are you ever

Re: mysql-native v2.1.0

On 03/07/2018 02:32 PM, bauss wrote: Wait why has it been updated to array() ? So it's not a real range anymore? Or was it always represented as an array behind the scenes? I just feel like allocating it into an additional array is a waste of memory? But if it was always like that I guess

Re: D for microservices

On Monday, 5 March 2018 at 17:58:25 UTC, Joakim wrote: On Monday, 5 March 2018 at 14:34:44 UTC, aberba wrote: [snip] The Alpine build is up, let me know if you have any problems. Note the changelog entry that says you'll need to install llvm and maybe other packages from the Alpine package

[Issue 18573] std.algorithm each does not function correctly for assignment under x86

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

Re: Gtk-D API Documentation now on dpldocs.info

On Thursday, 8 March 2018 at 01:27:07 UTC, Adam D. Ruppe wrote: GtkD is a D wrapper to the GTK library. It has plenty of doc comments attached... but they are in a special GTK syntax and all the cross references refer to C structs and functions instead of to D classes and methods. Well,

Re: Can't "is null" an interface?!?! Incompatible types???

On Thursday, 8 March 2018 at 04:48:08 UTC, Nick Sabalausky (Abscissa) wrote: - import vibe.core.net; TCPConnection mySocket; void main() { auto b = mySocket is null; } - That's giving me: - Error: incompatible types for

4 types of applications that can be created using java programming

Hello Guys, Having more than 3 years experience at MindMajix.com in IT professional with expertise in providing Enterprise Performance Engineering solutions & Integrated end to end IT monitoring solutions to clients from various industries. 1) Standalone Application It is also known as

Re: docs/definition: !object

Nick Sabalausky (Abscissa) wrote: (Or does return the address of the *reference* to the object rather than the address of the object?...You can see just how often I do OO in D ;) ) exactly. if you want to convert object to a pointer safely, do this: MyObject o; void* p =

Re: docs/definition: !object

On 03/08/2018 12:05 AM, ketmar wrote: Nick Sabalausky (Abscissa) wrote: I'm having trouble finding the documentation for what exactly the unary "not" operator does when applied to a class/interface object. Does this documentation exist somewhere? I know at least part of it involves "is

[Issue 18579] New: No group separators for floating point number formatted with zero decimal digits

https://issues.dlang.org/show_bug.cgi?id=18579 Issue ID: 18579 Summary: No group separators for floating point number formatted with zero decimal digits Product: D Version: D2 Hardware: All OS: All

Re: docs/definition: !object

Nick Sabalausky (Abscissa) wrote: I'm having trouble finding the documentation for what exactly the unary "not" operator does when applied to a class/interface object. Does this documentation exist somewhere? I know at least part of it involves "is null", but I seem to remember hearing

[Issue 18578] New: First enum value assigned 0 instead of EnumBaseType.init

https://issues.dlang.org/show_bug.cgi?id=18578 Issue ID: 18578 Summary: First enum value assigned 0 instead of EnumBaseType.init Product: D Version: D2 Hardware: All URL: https://dlang.org/spec/enum.html

Re: VsCode tutorial

On Wednesday, 7 March 2018 at 21:39:09 UTC, Apocalypto wrote: Are there any tutorials about D in vscode? No that I know of. Which are the minimal plugins to install to have code completion, syntax highlighting and code formatting? I've been getting by with

docs/definition: !object

I'm having trouble finding the documentation for what exactly the unary "not" operator does when applied to a class/interface object. Does this documentation exist somewhere? I know at least part of it involves "is null", but I seem to remember hearing there was more to it than just that.

Can't "is null" an interface?!?! Incompatible types???

- import vibe.core.net; TCPConnection mySocket; void main() { auto b = mySocket is null; } - That's giving me: - Error: incompatible types for (mySocket) is (null): TCPConnection and typeof(null) - WTF?!?!

Re: Vtable for virtual functions in D

On Wednesday, 7 March 2018 at 22:02:17 UTC, sarn wrote: When I wrote Xanthe a year ago, I rolled my own classes using alias this and explicit vtables: https://gitlab.com/sarneaud/xanthe/blob/master/src/game/rigid_body.d#L15 (I did this because normal D classes use the druntime library, and

[Issue 18221] DMD64 2.078.0 compile time explodes with -inline (>4X)

https://issues.dlang.org/show_bug.cgi?id=18221 Илья Ярошенко changed: What|Removed |Added Keywords||performance --

[Issue 18221] DMD64 2.078.0 compile time explodes with -inline (>4X)

https://issues.dlang.org/show_bug.cgi?id=18221 --- Comment #2 from Илья Ярошенко --- Mir Algorithm tests are a huge chunk of a super generic code. The same problem exists for a ultra Phobos-idiomatic code based on std.range and std.algorithm. --

[Issue 18221] DMD64 2.078.0 compile time explodes with -inline (>4X)

https://issues.dlang.org/show_bug.cgi?id=18221 Илья Ярошенко changed: What|Removed |Added Summary|DMD64 2.078.0 compile time |DMD64 2.078.0

Re: Fact check: when did D add static if?

On Thursday, 8 March 2018 at 04:12:12 UTC, Adam D. Ruppe wrote: On Thursday, 8 March 2018 at 04:09:17 UTC, Meta wrote: Has D had static if since its inception, or was it added somewhere along the way? https://digitalmars.com/d/1.0/changelog1.html What's New for D 0.124 May 19, 2005

Re: Fact check: when did D add static if?

On Thursday, 8 March 2018 at 04:09:17 UTC, Meta wrote: Has D had static if since its inception, or was it added somewhere along the way? https://digitalmars.com/d/1.0/changelog1.html What's New for D 0.124 May 19, 2005 New/Changed Features *snip* Added static if. That's before my

Fact check: when did D add static if?

Has D had static if since its inception, or was it added somewhere along the way?

Release: nanovega.d rendering lib like html5 canvas

https://github.com/adamdruppe/arsd nanovega.d depends on: simpledisplay.d, color.d, and ttf.d (latter only on Windows) Should also be present in v1.3 of the dub package http://code.dlang.org/packages/arsd-official API docs (includes an example to get you started)

[Issue 18577] New: Loose isForwardRange

https://issues.dlang.org/show_bug.cgi?id=18577 Issue ID: 18577 Summary: Loose isForwardRange Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement Priority: P1

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 --- Comment #31 from Shachar Shemesh --- Here goes: (In reply to Andrei Alexandrescu from comment #30) > Indeed it seems we are not supporting registration by address with ease for > D value types. Make that: at all. I understand

Re: DWT API Documentation now on dpldocs.info

On Thursday, 8 March 2018 at 01:34:12 UTC, Bill Baxter wrote: The logo in the corner - http://dwt.dpldocs.info/d-logo.png is a 404 btw. Yeah, I realized after generating the files that I used the wrong header source. The search is a broken link too... All fixed now via some hacky redirects

Re: #dbugfix: Unclear error message when trying to inherit from multiple classes

On Wednesday, 7 March 2018 at 22:23:59 UTC, Meta wrote: https://issues.dlang.org/show_bug.cgi?id=18574 Noted!

Re: Diamond Full-stack MVC / Template Engine - v2.7.0 Released!

On Wednesday, 7 March 2018 at 22:37:36 UTC, bauss wrote: I finally got around and fixed the last corners here and there. If you wonder what Diamond is, then it's a library for developing full-stack MVC web-applications based on vibe.d. It contains a lot of features (Which you can see in the

Re: DWT API Documentation now on dpldocs.info

The logo in the corner - http://dwt.dpldocs.info/d-logo.png -- is a 404 btw. On Wed, Mar 7, 2018 at 5:32 PM, Bill Baxter wrote: > Cool! I used to love using DWT back in the day. > > Yeh the Eclipse ones look like they were written by someone trying very > hard to make you

Re: DWT API Documentation now on dpldocs.info

Cool! I used to love using DWT back in the day. Yeh the Eclipse ones look like they were written by someone trying very hard to make you think you were using a native app on some platform with a horrible UI from the 90s. --bb On Wed, Mar 7, 2018 at 5:28 PM, Adam D. Ruppe via

Gtk-D API Documentation now on dpldocs.info

GtkD is a D wrapper to the GTK library. It has plenty of doc comments attached... but they are in a special GTK syntax and all the cross references refer to C structs and functions instead of to D classes and methods. Well, adrdox got some special-case code to handle this and do the

Re: Gtk-D API Documentation now on dpldocs.info

Compare and contrast to the official gtk-d docs: https://api.gtkd.org/gtkd/gtk/AboutDialog.html and the C gtk docs: https://developer.gnome.org/gtk3/stable/GtkApplication.html You can see they are all generated from the same source doc comments, but I think mine is nicest - just translating

Re: DWT API Documentation now on dpldocs.info

Compare and contrast with the official Java dox: http://help.eclipse.org/luna/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/api/org/eclipse/swt/package-summary.html both are generated from basically the same doc comments, but I like mine better :)

DWT API Documentation now on dpldocs.info

As some of you might know, DWT is a D port of Java's SWT. It is as thus nearly identical and you can use Java's documentation with very little effort - copy/paste of Java examples almost just work as D too. But, the eclipse docs are meh and besides, it is nice to have the D docs anyway.

Re: why not use git rebase instead of git merge in dlang repos?

On Wednesday, 7 March 2018 at 22:28:26 UTC, ketmar wrote: H. S. Teoh wrote: I've pestered Brad about it before, but the real trouble is the Mailman software. If you feel motivated enough, pestering the upstream Mailman authors about it might actually get us closer to fixing this problem, as

Re: #dbugfix: Unclear error message when trying to inherit from multiple classes

On Wednesday, 7 March 2018 at 22:23:59 UTC, Meta wrote: class Test: Foo, Bar, Baz { } class Foo {} class Bar {} class Baz {} Error: class `Test` base type must be interface, not Bar Error: class `Test` base type must be interface, not Baz I thought this error message used to be a lot better;

[Issue 18221] DMD64 2.078.0 compile time explodes with -inline for mir-algorithm (>4X)

https://issues.dlang.org/show_bug.cgi?id=18221 Timothee Cour changed: What|Removed |Added Summary|DMD64 2.078.0 compile time |DMD64 2.078.0

[Issue 18221] DMD64 2.078.0 compile time explodes with -inline for mir-algorithm

https://issues.dlang.org/show_bug.cgi?id=18221 Timothee Cour changed: What|Removed |Added CC|

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 Walter Bright changed: What|Removed |Added See Also|

[Issue 18576] Compiler not doing RVO with auto returns

https://issues.dlang.org/show_bug.cgi?id=18576 Walter Bright changed: What|Removed |Added See Also|

[Issue 17448] Move semantics cause memory corruption and cryptic bugs

https://issues.dlang.org/show_bug.cgi?id=17448 Walter Bright changed: What|Removed |Added See Also|

[Issue 18575] making delegate from member function can lead to unsafe code

https://issues.dlang.org/show_bug.cgi?id=18575 Walter Bright changed: What|Removed |Added See Also|

[Issue 18576] New: Compiler not doing RVO with auto returns

https://issues.dlang.org/show_bug.cgi?id=18576 Issue ID: 18576 Summary: Compiler not doing RVO with auto returns Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal Priority:

[Issue 18573] std.algorithm each does not function correctly for assignment under x86

https://issues.dlang.org/show_bug.cgi?id=18573 Steven Schveighoffer changed: What|Removed |Added CC|

[Issue 18575] making delegate from member function can lead to unsafe code

https://issues.dlang.org/show_bug.cgi?id=18575 Walter Bright changed: What|Removed |Added Keywords||safe --

[Issue 18575] New: making delegate from member function can lead to unsafe code

https://issues.dlang.org/show_bug.cgi?id=18575 Issue ID: 18575 Summary: making delegate from member function can lead to unsafe code Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: Diamond Full-stack MVC / Template Engine - v2.7.0 Released!

And api documentation for the new version! http://diamond.dpldocs.info/v2.7.0/index.html

Re: LDC 1.8.0

On Sunday, 4 March 2018 at 22:37:21 UTC, kinke wrote: Hi everyone, on behalf of the LDC team, I'm glad to announce LDC 1.8. The highlights of this version in a nutshell: * Based on D 2.078.3. * New switch `-link-defaultlib-shared` to link against shared druntime/Phobos. * Plugins support,

Re: Documentation for any* dub package, any version

On Wednesday, 7 March 2018 at 22:47:48 UTC, bauss wrote: How would you go about updating docs? Either go to the url for the specific version you want like http://diamond.dpldocs.info/v2.7.0/index.html and it will download (once dub scrapes it anyway) or ping me and I'll manually update the

Re: Documentation for any* dub package, any version

On Friday, 2 March 2018 at 00:04:10 UTC, Adam D. Ruppe wrote: On Thursday, 1 March 2018 at 11:00:15 UTC, Jonas Drewsen wrote: Would be cool if you could add support for creating docs from any dub project stored on github and not only the ones on code.dlang.org. That might be possible too.

llvm-mca: a static performance analysis tool

I find this such great LLVM news that I'd share it here: llvm-mca: a static performance analysis tool http://lists.llvm.org/pipermail/llvm-dev/2018-March/121490.html cheers, Johan

Diamond Full-stack MVC / Template Engine - v2.7.0 Released!

I finally got around and fixed the last corners here and there. If you wonder what Diamond is, then it's a library for developing full-stack MVC web-applications based on vibe.d. It contains a lot of features (Which you can see in the READ ME) To name a few of the key features: * Full

Re: why not use git rebase instead of git merge in dlang repos?

H. S. Teoh wrote: I've pestered Brad about it before, but the real trouble is the Mailman software. If you feel motivated enough, pestering the upstream Mailman authors about it might actually get us closer to fixing this problem, as it really isn't a problem on Brad's end either. It's not

#dbugfix: Unclear error message when trying to inherit from multiple classes

class Test: Foo, Bar, Baz { } class Foo {} class Bar {} class Baz {} Error: class `Test` base type must be interface, not Bar Error: class `Test` base type must be interface, not Baz I thought this error message used to be a lot better; along the lines of "D does not support multiple

Re: why not use git rebase instead of git merge in dlang repos?

On Thu, Mar 08, 2018 at 12:10:28AM +0200, ketmar via Digitalmars-d wrote: > Seb wrote: > > > OT: I don't know what you are doing, but you seem to be the only one > > who always creates new threads when replying. I assume you use nntp? > > Maybe something wrong with your client? > > it was

[Issue 18574] New: Unclear error message when trying to inherit from multiple classes

https://issues.dlang.org/show_bug.cgi?id=18574 Issue ID: 18574 Summary: Unclear error message when trying to inherit from multiple classes Product: D Version: D2 Hardware: All OS: All Status: NEW

Re: Vtable for virtual functions in D

On Wed, Mar 07, 2018 at 09:14:12PM +, Henrik via Digitalmars-d wrote: [...] > The direct support of C headers would be very convenient in migrating > parts of C/C++ projects to D. It would also open up POSIX which is > used extensively in our work. [...] There's already core.sys.posix.*,

Re: why not use git rebase instead of git merge in dlang repos?

Seb wrote: OT: I don't know what you are doing, but you seem to be the only one who always creates new threads when replying. I assume you use nntp? Maybe something wrong with your client? it was already discussed several times: this is the issue with mailing list processor: it cannot

Re: issue with each specifically for x86

Matt Gamble wrote: Ok, this has been submitted as a bug. https://issues.dlang.org/show_bug.cgi?id=18573 thank you.

[Issue 18573] std.algorithm each does not function correctly for assignment under x86

https://issues.dlang.org/show_bug.cgi?id=18573 Ketmar Dark changed: What|Removed |Added Component|phobos |dmd

Re: Vtable for virtual functions in D

On Wednesday, 7 March 2018 at 12:49:40 UTC, Guillaume Piolat wrote: If you know enough D maybe you can implement your own virtual functions on top of D structs. It seems no one has made it yet. When I wrote Xanthe a year ago, I rolled my own classes using alias this and explicit vtables:

[Issue 18573] std.algorithm each does not function correctly for assignment under x86

https://issues.dlang.org/show_bug.cgi?id=18573 --- Comment #1 from Ketmar Dark --- some clarification: basically, this boils down to codegen bug: if we have function that returns some floating point value, and FPU is involved, and caller does `cast(void)myfunc()`, result

[Issue 18573] std.algorithm each does not function correctly for assignment under x86

https://issues.dlang.org/show_bug.cgi?id=18573 Ketmar Dark changed: What|Removed |Added CC|

Re: why not use git rebase instead of git merge in dlang repos?

On Wednesday, 7 March 2018 at 21:03:52 UTC, H. S. Teoh wrote: On Wed, Mar 07, 2018 at 12:42:52PM -0800, Timothee Cour via Digitalmars-d wrote: [...] On the contrary, I find using merge is easier to understand, because it shows clearly individual commits within a single PR, and also a linear

Re: mysql-native v2.1.0

On Wednesday, 7 March 2018 at 19:36:57 UTC, bauss wrote: On Wednesday, 7 March 2018 at 11:04:10 UTC, Nick Sabalausky (Abscissa) wrote: On 03/06/2018 01:31 PM, bauss wrote: I can't seem to find any examples on how they were updated and what exactly to change in my code. Also, FWIW,

Re: issue with each specifically for x86

On Wednesday, 7 March 2018 at 21:39:58 UTC, ketmar wrote: Matt Gamble wrote: On Wednesday, 7 March 2018 at 21:02:30 UTC, ag0aep6g wrote: On 03/07/2018 09:09 PM, ag0aep6g wrote: [...] With `real` instead of `double` x86_64 is also affected. Wow. Good to know I'm not crazy. I was afk for a

[Issue 18573] std.algorithm each does not function correctly for assignment under x86

https://issues.dlang.org/show_bug.cgi?id=18573 Matthew Gamble changed: What|Removed |Added Severity|enhancement |normal --

[Issue 18573] New: std.algorithm each does not function correctly for assignment under x86

https://issues.dlang.org/show_bug.cgi?id=18573 Issue ID: 18573 Summary: std.algorithm each does not function correctly for assignment under x86 Product: D Version: D2 Hardware: x86 OS: Windows

Re: issue with each specifically for x86

Matt Gamble wrote: On Wednesday, 7 March 2018 at 21:02:30 UTC, ag0aep6g wrote: On 03/07/2018 09:09 PM, ag0aep6g wrote: double f() { return 1; } void main() {     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();    

VsCode tutorial

Are there any tutorials about D in vscode? Which are the minimal plugins to install to have code completion, syntax highlighting and code formatting? Are there any app templates that i can invoke to not start every project from scratch? How can I debug my app?

Re: issue with each specifically for x86

On Wednesday, 7 March 2018 at 21:02:30 UTC, ag0aep6g wrote: On 03/07/2018 09:09 PM, ag0aep6g wrote: double f() { return 1; } void main() {     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();   

Re: Advent of D

On Tue, 2018-03-06 at 18:09 +, Jordi Gutiérrez Hermoso via Digitalmars-d wrote: > I wrote a blog post about working on Advent of Code in D. You can > read it here: > > http://jordi.inversethought.com/blog/advent-of-d/ Another blog post deserving of formal publication in an ACCU journal. --

Re: Vtable for virtual functions in D

Hi everyone, thank you all for your great answers. I'm playing around with @nogc right now, and it looks really promising. Strings and static arrays all seem to be located on the stack, which is so much better compared to std::string and std::vector in C++. The double indirection for virtual

Re: issue with each specifically for x86

ag0aep6g wrote: On 03/07/2018 09:09 PM, ag0aep6g wrote: double f() { return 1; } void main() {     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     double b = 2;     assert(b == 2); /*

Re: issue with each specifically for x86

On 03/07/2018 09:09 PM, ag0aep6g wrote: double f() { return 1; } void main() {     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     double b = 2;     assert(b == 2); /* fails; should pass

Re: why not use git rebase instead of git merge in dlang repos?

On Wed, Mar 07, 2018 at 12:42:52PM -0800, Timothee Cour via Digitalmars-d wrote: > There are lots of articles on this topic, eg: > https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/ > (note that squashing down to 1 commit shouldn't be necessary but at > least

Re: issue with each specifically for x86

H. S. Teoh wrote: On Wed, Mar 07, 2018 at 10:21:42PM +0200, ketmar via Digitalmars-d-learn wrote: [...] it looks like ignoring `double` result causes FPU stack imbalance ('cause compiler doesn't insert "FPU pop" instruction), and that affects the computations. on 64 bit it doesn't matter,

[Issue 18161] std.algorithm.iteration.chunkBy should be usable in @safe

https://issues.dlang.org/show_bug.cgi?id=18161 Jack Stouffer changed: What|Removed |Added CC||j...@jackstouffer.com

Re: issue with each specifically for x86

H. S. Teoh wrote: On Wed, Mar 07, 2018 at 10:21:42PM +0200, ketmar via Digitalmars-d-learn wrote: [...] it looks like ignoring `double` result causes FPU stack imbalance ('cause compiler doesn't insert "FPU pop" instruction), and that affects the computations. on 64 bit it doesn't matter,

why not use git rebase instead of git merge in dlang repos?

There are lots of articles on this topic, eg: https://blog.carbonfive.com/2017/08/28/always-squash-and-rebase-your-git-commits/ (note that squashing down to 1 commit shouldn't be necessary but at least rebasing should be done) github UI also allows to rebase (instead of merge) would really

Re: issue with each specifically for x86

On Wed, Mar 07, 2018 at 10:21:42PM +0200, ketmar via Digitalmars-d-learn wrote: [...] > it looks like ignoring `double` result causes FPU stack imbalance > ('cause compiler doesn't insert "FPU pop" instruction), and that > affects the computations. > > on 64 bit it doesn't matter, 'cause no FPU

Re: Two things I thought would be simple

On 07.03.2018 18:23, Jonathan M Davis wrote: However, even doing something like auto func2(Parameters!func args = AliasSeq!(1, 2, 3)) { return func(args); } doesn't work properly. If that version of the function is used, then the call which passes all three arguments compiles, but the

[Issue 18572] New: AliasSeq default arguments are broken

https://issues.dlang.org/show_bug.cgi?id=18572 Issue ID: 18572 Summary: AliasSeq default arguments are broken Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: normal Priority: P1

Re: issue with each specifically for x86

Steven Schveighoffer wrote: it seems that the only difference between `void` and `double` lambda is one asm instruction: `fldl (%edi)`. it is presend in `double` labmda, and absent in `void` lambda. it looks like ignoring `double` result causes FPU stack imbalance ('cause compiler doesn't

Advent of D

On Wednesday, 7 March 2018 at 16:34:31 UTC, Pradeep Gowda wrote: https://lobste.rs/t/d Please do not forget to tag your D related submissions with the "D" tag. and a blog post: https://lobste.rs/s/b4qki7/advent_d

Re: issue with each specifically for x86

On 3/7/18 3:09 PM, ag0aep6g wrote: On 03/07/2018 08:54 PM, Steven Schveighoffer wrote: Clearly there is some codegen issue here. It's beautiful: double f() { return 1; } void main() {     cast(void) f();     cast(void) f();     cast(void) f();     cast(void) f();     cast(void)

Re: How can I get notified when an process created by spawnShell() has exit?

On Wednesday, 7 March 2018 at 15:03:28 UTC, Marc wrote: I do need to start (up to 4 a time) processes in parallel but I'd like to get notified (similar to C#'s Process.Exited Event) when the process exits. How can I do that in D? You can use pipeShell and a control loop to check when the

Re: issue with each specifically for x86

On 03/07/2018 08:54 PM, Steven Schveighoffer wrote: Looking at each, it looks like it does this: cast(void) unaryFun!pred(r.front); So I tried this: auto pred = i => a[i] = a[i-1] + 2; foreach(i; 1 .. a.length)    cast(void)pred(i); And I see the -nan value. Remove the cast(void) and I

Re: issue with each specifically for x86

On 3/7/18 1:57 PM, Matt Gamble wrote: This is a record for me with two 32bit vs 64bit issues in one day. Seems to be a problem with using "each" under 32bit which can be fixed by using foreach or switching to x64. Am I doing something wrong or is this the second bug I've found today? Below

Re: mysql-native v2.1.0

On Wednesday, 7 March 2018 at 11:04:10 UTC, Nick Sabalausky (Abscissa) wrote: On 03/06/2018 01:31 PM, bauss wrote: I can't seem to find any examples on how they were updated and what exactly to change in my code. Also, FWIW, mysql-native uses semantic versioning (semver), so anything

Re: mysql-native v2.1.0

On Wednesday, 7 March 2018 at 10:14:08 UTC, Nick Sabalausky (Abscissa) wrote: On 03/06/2018 01:54 PM, bauss wrote: On Tuesday, 6 March 2018 at 18:36:45 UTC, bauss wrote: Like more specifically do I still call lockConnection() on a MySQLPool? If you're using vibe.d and MySQLPool, then yes.

[Issue 9297] Formatting of floating point values in std.format truncates reals to double

https://issues.dlang.org/show_bug.cgi?id=9297 Steven Schveighoffer changed: What|Removed |Added CC|

[Issue 18570] exp function does not work correctly for real in 64bit Windows

https://issues.dlang.org/show_bug.cgi?id=18570 Steven Schveighoffer changed: What|Removed |Added Status|NEW |RESOLVED

Re: issue with each specifically for x86

On 03/07/2018 10:57 AM, Matt Gamble wrote: This is a record for me with two 32bit vs 64bit issues in one day. Seems to be a problem with using "each" under 32bit which can be fixed by using foreach or switching to x64. Am I doing something wrong or is this the second bug I've found today?

  1   2   3   >