Re: requests module generates " Can't parse uri '' "

2019-11-07 Thread cartland via Digitalmars-d-learn
On Friday, 8 November 2019 at 03:43:52 UTC, Adam D. Ruppe wrote: On Friday, 8 November 2019 at 03:36:22 UTC, cartland wrote: * snip * huh, idk, it works when I try that exact code in a fresh project * snip * are you behind a proxy or something maybe? Thanks for checking. I'm not behind a p

Re: requests module generates " Can't parse uri '' "

2019-11-07 Thread Adam D. Ruppe via Digitalmars-d-learn
On Friday, 8 November 2019 at 03:36:22 UTC, cartland wrote: * snip * huh, idk, it works when I try that exact code in a fresh project dub init dub add requests # edit source/app.d to have your contents dub run and it spat out the content... are you behind a proxy or something maybe?

Re: requests module generates " Can't parse uri '' "

2019-11-07 Thread cartland via Digitalmars-d-learn
On Friday, 8 November 2019 at 03:31:56 UTC, Adam D. Ruppe wrote: On Friday, 8 November 2019 at 03:29:41 UTC, cartland wrote: When I run dub, I get What was your main() code? The error makes me think you might have just tried like get("") or something import std.stdio; import requests; voi

Re: requests module generates " Can't parse uri '' "

2019-11-07 Thread Adam D. Ruppe via Digitalmars-d-learn
On Friday, 8 November 2019 at 03:29:41 UTC, cartland wrote: When I run dub, I get What was your main() code? The error makes me think you might have just tried like get("") or something

requests module generates " Can't parse uri '' "

2019-11-07 Thread cartland via Digitalmars-d-learn
First time D use :) After dub init, I used the example from https://code.dlang.org/packages/requests and ran "dub add requests" When I run dub, I get requests.uri.UriException@/home/cartland/.dub/packages/requests-1.0.9/requests/source/requests/uri.d(35): Can't parse uri '' Full output on

Re: Using an async buffer

2019-11-07 Thread Ali Çehreli via Digitalmars-d-learn
On 11/07/2019 07:07 AM, bioinfornatics wrote: > Dear, > > I try to use the async buffer describe into std.parallelism > documentation but my test code core dump! I admit I don't fully understand the lifetime issues but removing the "code smell" of the modul-level File object solved the issue for

Re: Linker anomalies

2019-11-07 Thread user5678 via Digitalmars-d-learn
On Thursday, 7 November 2019 at 12:14:43 UTC, Luh wrote: Hey there, I figured out some strange behavior ; #1 It seems that the linker doesn't check for the function declared twice first. Instead, it says: "Error: class app.Child use of app.Parent.foo() is hidden by Child; use alias foo = Pa

Re: Linker anomalies

2019-11-07 Thread Luh via Digitalmars-d-learn
On Thursday, 7 November 2019 at 18:45:21 UTC, Ali Çehreli wrote: On 11/07/2019 04:14 AM, Luh wrote: It's not the linker but the "compiler" that is concerned about these things. [...] Oops :o That's an important warning where the programmer can get surprising results depending on whether th

Re: Linker anomalies

2019-11-07 Thread Ali Çehreli via Digitalmars-d-learn
On 11/07/2019 04:14 AM, Luh wrote: > Hey there, > > I figured out some strange behavior ; > > #1 > It seems that the linker doesn't check for the function declared twice > first. It's not the linker but the "compiler" that is concerned about these things. > Instead, it says: > > "Error: class ap

Using an async buffer

2019-11-07 Thread bioinfornatics via Digitalmars-d-learn
Dear, I try to use the async buffer describe into std.parallelism documentation but my test code core dump! documentation: https://dlang.org/phobos/std_parallelism.html#.TaskPool.asyncBuf.2 snipptet: https://paste.fedoraproject.org/paste/K5W1O1dLzZ0sPV8NeGztUg Trace: $ gdb test (gdb) r

Linker anomalies

2019-11-07 Thread Luh via Digitalmars-d-learn
Hey there, I figured out some strange behavior ; #1 It seems that the linker doesn't check for the function declared twice first. Instead, it says: "Error: class app.Child use of app.Parent.foo() is hidden by Child; use alias foo = Parent.foo; to introduce base class overload set" but whe