[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

--- Comment #11 from Vladimir Panteleev  ---
 ag0aep6g: Since implementing -c directly is more complicated with the recent
changes, can we emulate by using -lib and extracting the lib file's contents or
such?

Timothee, can you substitute -c with -lib in your use case? If so, we could fix
the -od problem and make -c an explicitly unsupported switch like -o-.

--

[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

Andrei Alexandrescu  changed:

   What|Removed |Added

 CC||and...@erdani.com

--- Comment #10 from Andrei Alexandrescu  ---
It may indeed be worthwhile to support -c as in "solve all dependencies and
produce a big .o file ready for linking". There is no easy way to do that with
either dmd or rdmd. Alternatively we could use a --no-link flag but -c seems
more direct. Vladimir, what do you think?

--

[Issue 5710] cannot use delegates as parameters to non-global template

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=5710

--- Comment #42 from Martin Nowak  ---
I'm hearing that C++ closures simply pass one pointer/reference for each
referenced variable, which does support an arbitrary amount of contexts.
Sounds interesting.

--

[Issue 5710] cannot use delegates as parameters to non-global template

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=5710

Martin Nowak  changed:

   What|Removed |Added

 OS|Windows |All

--

[Issue 11274] Use a CDN for dlang.org

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=11274

--- Comment #5 from greenify  ---

Adding some thoughts of mine to the discussion:

> As a user, CloudFlare hasn't been very nice. While I still used the Opera 12 
> browser, I would get hit by CloudFlare CAPTCHAs very regularly. Apparently I 
> was being "punished" for having an unusual user-agent. For this reason, I 
> have set CloudFlare's protection setting to "essentially none" on my 
> websites, with no noticeable negative effect.

Yep I have experienced this as well :/

> I think we should consider using a CDN when we actually start feeling that we 
> need to. As far as I know our uptime and response time has been pretty good, 
> and we don't host a lot of assets (large images or such) that would benefit a 
> lot from a CDN.

We have quite some troubles with it on Travis in terms of reliability and I
think our "fast" pageload could even improved ;-)
In fact if one looks at these page checkers, e.g.

https://tools.pingdom.com/#!/RHG4Q/dlang.org
https://gtmetrix.com/reports/dlang.org/5AUbSaw8
https://developers.google.com/speed/pagespeed/insights/?url=dlang.org

There are a couple of other things one could do, e.g:

- leverage browser caching
- optimize images
- serve scaled images
- enable compression
- minify CSS & javascript

> When we do need to, and should we pick CloudFlare, I recommend to also set 
> the protection level to the minimum, as we have no dynamic content to protect 
> and as such the user frustration from false positives is not worth it.

Speaking of no dynamic content: as we have nearly no dynamic content, we could
also think about using S3, GitHub Pages (free) or similar for dlang.org.
AFAIK GitHub Pages also come with a CDN.

> FWIW, it's worth considering that the reason why CloudFlare's free plan is 
> profitable is likely because it grants them a ton of analytics into users' 
> browsing habits, so if user privacy is of any consideration that would be one 
> downside.

There's also the Amazon CloudFront CDN (and others), but one needs to pay per
traffic and IIRC it isn't that cheap.

--

[Issue 11274] Use a CDN for dlang.org

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=11274

--- Comment #4 from Vladimir Panteleev  ---
(In reply to Martin Nowak from comment #3)
> For an opionion I'd hope to draw a bit on Vladimir's vast experience for
> this (CC).

Hmm, I wouldn't really say my experience is that vast...

As a webmaster, I do have a website with a lot of hits behind CloudFlare's free
plan. I haven't encountered any issues with it, and it pretty much works as
advertised.

As a user, CloudFlare hasn't been very nice. While I still used the Opera 12
browser, I would get hit by CloudFlare CAPTCHAs very regularly. Apparently I
was being "punished" for having an unusual user-agent. For this reason, I have
set CloudFlare's protection setting to "essentially none" on my websites, with
no noticeable negative effect.

I think we should consider using a CDN when we actually start feeling that we
need to. As far as I know our uptime and response time has been pretty good,
and we don't host a lot of assets (large images or such) that would benefit a
lot from a CDN. When we do need to, and should we pick CloudFlare, I recommend
to also set the protection level to the minimum, as we have no dynamic content
to protect and as such the user frustration from false positives is not worth
it.

FWIW, it's worth considering that the reason why CloudFlare's free plan is
profitable is likely because it grants them a ton of analytics into users'
browsing habits, so if user privacy is of any consideration that would be one
downside.

--

[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

--- Comment #9 from Timothee Cour  ---
>> Sorry, what is the use case of using -c ? I think it working was a mere 
>> accident. If you want to syntax-check the file, use dmd (not rdmd) with -o-. 
>> Or do you want to compile everything into a single object file for some 
>> reason?

Use case: when dmd's built-in linker magic isn't good enough (eg 
http://forum.dlang.org/post/mailman.765.1481492407.9448.digitalmar...@puremagic.com
where i have to first compile then link to get -pie but I keep running into
similar issues where i want to link seperately because the default isn't good
enough)

--

[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

--- Comment #8 from Vladimir Panteleev  ---
There is a known problem with -lib and -od:

https://issues.dlang.org/show_bug.cgi?id=14296

Admittedly it's my fault as my commit introduced the regression, however the
underlying bug is that DMD treats -od differently depending on whether -lib is
passed or not, which I did not expect.

--

[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

Vladimir Panteleev  changed:

   What|Removed |Added

 CC||thecybersha...@gmail.com

--- Comment #7 from Vladimir Panteleev  ---
Sorry, what is the use case of using -c ? I think it working was a mere
accident. If you want to syntax-check the file, use dmd (not rdmd) with -o-. Or
do you want to compile everything into a single object file for some reason?

--

[Issue 11274] Use a CDN for dlang.org

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=11274

Martin Nowak  changed:

   What|Removed |Added

 CC||c...@dawg.eu,
   ||thecybersha...@gmail.com

--- Comment #3 from Martin Nowak  ---
We could easily do the experiment though, if we know how to objectively monitor
the problems/performance.
Reachability should be the most important metric, followed by search ranking,
and website speed.
For an opionion I'd hope to draw a bit on Vladimir's vast experience for this
(CC).

--

[Issue 11274] Use a CDN for dlang.org

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=11274

--- Comment #2 from Martin Nowak  ---
Caches come with their own problems and they often block for
longer times with 5xx screens, for even smallest backend hickups. So my
experience is that they easily worsen reachability if you're already
having a few issues.

--

[Issue 16955] std.process.spawnProcessImpl can crash due to alloca

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16955

--- Comment #2 from github-bugzi...@puremagic.com ---
Commits pushed to master at https://github.com/dlang/phobos

https://github.com/dlang/phobos/commit/aec837beca951d6e7194e93a08de6cb375230e42
Fix Issue 16955 - std.process.spawnProcessImpl can crash due to alloca

https://github.com/dlang/phobos/commit/43a4d2cc1e879cbcd1809bfac765c6fef2532cb3
Merge pull request #4934 from John-Colvin/fix_spawn

Fix Issue 16955 - std.process.spawnProcessImpl can crash due to alloca

--

[Issue 16955] std.process.spawnProcessImpl can crash due to alloca

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16955

github-bugzi...@puremagic.com changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

--

[Issue 16963] Wrong label name resolution in asm statement

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16963

safety0ff.bugz  changed:

   What|Removed |Added

   Keywords||iasm
 CC||safety0ff.b...@gmail.com

--

[Issue 16963] Wrong label name resolution in asm statement

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16963

ag0ae...@gmail.com changed:

   What|Removed |Added

   Keywords||wrong-code
 CC||ag0ae...@gmail.com
 OS|Windows |All

--

[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

ag0ae...@gmail.com changed:

   What|Removed |Added

 CC||ag0ae...@gmail.com

--- Comment #6 from ag0ae...@gmail.com ---
Found another one while looking into this:
https://issues.dlang.org/show_bug.cgi?id=16966

Regarding the bugs here:

The -of=/-od= thing (comment 3) seems to be a simple oversight. rdmd has just
not been thought of when the feature was implemented in dmd. Should be easy to
fix.

-o- not working (comment 2) seems to a deliberate restriction.

Supporting -c as in the summary may be some work. I must have missed that
scenario completely when doing .
Problem is that rdmd now treats the root module specially: compiles it
separately, links everything together in a separate step. That doesn't go
naturally with -c, as far as I see. May have to detect -c and do things
completely different then.

-lib not working with relative paths (comment 3) seems odd. I hope it's just a
simple bug, and not a design flaw. I haven't investigated.

I'm going to look into this further, but it may take me a while. If anyone else
wants to have a go, that would be great.

--

[Issue 16966] rdmd: AssertError@rdmd.d(489): should have been created by compileRootAndGetDeps

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16966

ag0ae...@gmail.com changed:

   What|Removed |Added

   Keywords||pull
   Assignee|nob...@puremagic.com|ag0ae...@gmail.com

--- Comment #1 from ag0ae...@gmail.com ---
(In reply to ag0aep6g from comment #0)
> I'm working on a PR.

https://github.com/dlang/tools/pull/204

--

[Issue 16966] New: rdmd: AssertError@rdmd.d(489): should have been created by compileRootAndGetDeps

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16966

  Issue ID: 16966
   Summary: rdmd: AssertError@rdmd.d(489): should have been
created by compileRootAndGetDeps
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: normal
  Priority: P1
 Component: tools
  Assignee: nob...@puremagic.com
  Reporter: ag0ae...@gmail.com

test.d:

void main() {}


Run with rdmd, then try --build-only:

rdmd test.d
rdmd --build-only test.d


Output:

core.exception.AssertError@rdmd.d(489): should have been created by
compileRootAndGetDeps


I'm working on a PR.

--

[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

--- Comment #5 from Andrej Mitrovic  ---
(In reply to Andrej Mitrovic from comment #4)
> https://github.com/dlang/tools/commit/
> a63233c22dce33ff91141c5706cdc7d66a8c0099 seems to have caused the regression
> for the first test-case.

That's a merge commit, it was specifically 10ca158.

--

[Issue 16962] rdmd --build-only --force -c main.d fails: ./main: No such file or directory

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16962

Andrej Mitrovic  changed:

   What|Removed |Added

 CC||andrej.mitrov...@gmail.com

--- Comment #4 from Andrej Mitrovic  ---
https://github.com/dlang/tools/commit/a63233c22dce33ff91141c5706cdc7d66a8c0099
seems to have caused the regression for the first test-case.

--

[Issue 16965] changed.d compile error

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16965

--- Comment #1 from rdirect...@gmail.com ---
Created attachment 1625
  --> https://issues.dlang.org/attachment.cgi?id=1625=edit
git diff patch

--

[Issue 16965] changed.d compile error

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16965

rdirect...@gmail.com changed:

   What|Removed |Added

URL||https://github.com/dlang/to
   ||ols/blob/master/changed.d#L
   ||77

--

[Issue 16965] New: changed.d compile error

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=16965

  Issue ID: 16965
   Summary: changed.d compile error
   Product: D
   Version: D2
  Hardware: x86_64
OS: Linux
Status: NEW
  Severity: normal
  Priority: P1
 Component: tools
  Assignee: nob...@puremagic.com
  Reporter: rdirect...@gmail.com

Created attachment 1624
  --> https://issues.dlang.org/attachment.cgi?id=1624=edit
screenshot of compile state after change

changed.d(77): Error: variable changed.getIssues.closedRE : Unable to
initialize enum with class or pointer to struct. Use static const variable
instead.

I edited line 77
enum closedRE = ctRegex!(`((close|fix|address)e?(s|d)? )?(ticket|bug|tracker
item|issue)s?:? *([\d ,\+