OT: in economic terms Moore's Law is already dead

2019-07-17 Thread Laeeth Isharc via Digitalmars-d-learn
https://www.infoq.com/presentations/moore-law-expiring/ At the same time as the arrival of Optane persistent storage in relatively chest machines changes the game a bit. If storage prices do keep falling at 40% annualised or thereabouts, it's possible one might see a little more respect

Re: How would I know if AppVayer is parsing my yaml file?

2019-07-17 Thread Mike Brockus via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 18:42:20 UTC, Paul Backus wrote: On Wednesday, 17 July 2019 at 17:03:16 UTC, Mike Brockus wrote: If you never seen Meson before then pick up a camera and take a picture: 樂  https://mesonbuild.com/ Quick question. I started integrating ci/cd best practices to my

Re: can not find the error: Error: TypeInfo cannot be used with -betterC

2019-07-17 Thread Sebastiaan Koppe via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 15:52:39 UTC, Newbie2019 wrote: when build my project with -betterC, it throw this error: Error: TypeInfo cannot be used with -betterC There is no location information about it, how can I find what code cause this ? With ldc I often use -v to get the verbose

Re: __stdin.d(2): Error: found End of File when expecting }

2019-07-17 Thread Andre Pany via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 20:02:51 UTC, ag0aep6g wrote: On 17.07.19 21:05, Andre Pany wrote: [...] Check out what `echo $text` prints: import std; void main() { while(true) { string enemy1 = readln().strip; int dist1 = to!int(readln().strip); string enemy2 = readln().strip; int

Re: can not find the error: Error: TypeInfo cannot be used with -betterC

2019-07-17 Thread aliak via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 15:52:39 UTC, Newbie2019 wrote: when build my project with -betterC, it throw this error: Error: TypeInfo cannot be used with -betterC There is no location information about it, how can I find what code cause this ? You usually get that *extrememly* unhelpful

Re: __stdin.d(2): Error: found End of File when expecting }

2019-07-17 Thread ag0aep6g via Digitalmars-d-learn
On 17.07.19 21:05, Andre Pany wrote: ``` #!/bin/bash text=" import std; void main() {     while(true)     {     string enemy1 = readln().strip;     int dist1 = to!int(readln().strip);     string enemy2 = readln().strip;     int dist2 = to!int(readln().strip);    

Re: __stdin.d(2): Error: found End of File when expecting }

2019-07-17 Thread H. S. Teoh via Digitalmars-d-learn
On Wed, Jul 17, 2019 at 07:05:20PM +, Andre Pany via Digitalmars-d-learn wrote: > Hi, > > this scripts throws 2 times this error: > __stdin.d(2): Error: found End of File when expecting } following compound > statement > __stdin.d(2): Error: found End of File when expecting } following

Re: OPTLINK : Warning 9: Unknown Option : OUT

2019-07-17 Thread Anonymouse via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 17:43:53 UTC, Anonymouse wrote: [...] Ignore this, Logger is a class and the error is to be expected. Will retry dustmite.

__stdin.d(2): Error: found End of File when expecting }

2019-07-17 Thread Andre Pany via Digitalmars-d-learn
Hi, this scripts throws 2 times this error: __stdin.d(2): Error: found End of File when expecting } following compound statement __stdin.d(2): Error: found End of File when expecting } following compound statement ``` #!/bin/bash text=" import std; void main() { while(true) {

Re: How would I know if AppVayer is parsing my yaml file?

2019-07-17 Thread Paul Backus via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 17:03:16 UTC, Mike Brockus wrote: If you never seen Meson before then pick up a camera and take a picture: 樂  https://mesonbuild.com/ Quick question. I started integrating ci/cd best practices to my Meson projects and I was wondering how would I know if AppVayer

Re: OPTLINK : Warning 9: Unknown Option : OUT

2019-07-17 Thread Anonymouse via Digitalmars-d-learn
On Tuesday, 16 July 2019 at 13:33:01 UTC, Anonymouse wrote: I started a dustmite process, with some luck it should produce something smaller by tonight or tomorrow. Reduced: import std.experimental.logger : Logger; void main() { Logger logger; logger.error(); } git clone

How would I know if AppVayer is parsing my yaml file?

2019-07-17 Thread Mike Brockus via Digitalmars-d-learn
If you never seen Meson before then pick up a camera and take a picture: 樂  https://mesonbuild.com/ Quick question. I started integrating ci/cd best practices to my Meson projects and I was wondering how would I know if AppVayer is parsing my yaml file? I know I got a failed build because it

can not find the error: Error: TypeInfo cannot be used with -betterC

2019-07-17 Thread Newbie2019 via Digitalmars-d-learn
when build my project with -betterC, it throw this error: Error: TypeInfo cannot be used with -betterC There is no location information about it, how can I find what code cause this ?

Re: Error: @nogc function run cannot call non-@nogc destructor TcpServer.~this

2019-07-17 Thread Newbie2019 via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 12:16:54 UTC, Adam D. Ruppe wrote: It is also possible a member of the struct has a destructor that is triggering it. Thanks, I check all member and one of them is not @nogc nothrow. add @nogc nothrow to member fix it.

Re: Error: @nogc function run cannot call non-@nogc destructor TcpServer.~this

2019-07-17 Thread Adam D. Ruppe via Digitalmars-d-learn
It is also possible a member of the struct has a destructor that is triggering it.

Re: Error: @nogc function run cannot call non-@nogc destructor TcpServer.~this

2019-07-17 Thread ikod via Digitalmars-d-learn
On Wednesday, 17 July 2019 at 10:51:53 UTC, Newbie2019 wrote: this is very hard to made a minimal example, and the projects only build with ldc. There is a struct TcpServer has no destructor, and all method is @nogc nothrow. Then just add destructor with @nogc attribute.

Error: @nogc function run cannot call non-@nogc destructor TcpServer.~this

2019-07-17 Thread Newbie2019 via Digitalmars-d-learn
this is very hard to made a minimal example, and the projects only build with ldc. There is a struct TcpServer has no destructor, and all method is @nogc nothrow. but some how when I use it on function run @nogc nothrow, ldc report : @nogc function run cannot call non-@nogc destructor