[Issue 17596] dmd d 2.073.2 and 2.074.1 interim generated dmd segfaults on FreeBSD 12-CURRENT

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17596

Cy Schubert  changed:

   What|Removed |Added

   Priority|P1  |P2

--

[Issue 17380] Compiler segfaults on undefined symbol

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17380

--- Comment #2 from Walter Bright  ---
I don't think it is a regression, either.

https://github.com/dlang/dmd/pull/6969

--

[Issue 16992] ddoc generator does not insert ddoc-ed unittest blocks for fromISOString, fromISOExtString, and fromSimpleString into the documentation

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

Jonathan M Davis  changed:

   What|Removed |Added

   Keywords|trivial |ddoc
  Component|dlang.org   |dmd
   Severity|enhancement |normal

--

[Issue 16992] ddoc generator does not insert ddoc-ed unittest blocks for fromISOString, fromISOExtString, and fromSimpleString into the documentation

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

Jonathan M Davis  changed:

   What|Removed |Added

Summary|fromISOString,  |ddoc generator does not
   |fromISOExtString, and   |insert ddoc-ed unittest
   |fromSimpleString do not |blocks for fromISOString,
   |have examples   |fromISOExtString, and
   ||fromSimpleString into the
   ||documentation

--

[Issue 17380] Compiler segfaults on undefined symbol

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17380

Walter Bright  changed:

   What|Removed |Added

 CC||bugzi...@digitalmars.com
   Hardware|x86_64  |All
Summary|[REG 2.074.0] Compiler  |Compiler segfaults on
   |segfaults on undefined  |undefined symbol
   |symbol  |
 OS|Linux   |All
   Severity|regression  |normal

--

[Issue 16992] fromISOString, fromISOExtString, and fromSimpleString do not have examples

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

Jonathan M Davis  changed:

   What|Removed |Added

 CC||issues.dl...@jmdavisprog.co
   ||m

--- Comment #8 from Jonathan M Davis  ---
(In reply to RazvanN from comment #7)
> I think that having all fromISOString overloads gathered in a single
> template function which is called fromISOString!Choose_type(some_string),
> where Choose_type is one of {Date, DateTime, TimeOfDay} is more elegant and
> the documentation can be presented a single time; rather than having 3
> fromISOString functions dispersed through the documentation.

They're dispersed, because they go with each individual type and are specific
to each individual type. They have distinct implemnetations and should be
documented as such. I see no reason to have a module-level wrapper function -
especially when not all of the time point types are even in the same module
anymore, now that std.datetime has been split up.

The issue here is that the documentation examples do not show up in the
ddoc-generated documentation in spite of the fact that they are in the code as
ddoc-ed examples. There is no need to change std.datetime here. We need to fix
the compiler.

--

[Issue 17594] Define DDOC_BLANKLINE as an empty HTML paragraph, thus obviating the need to wrap text in $(P ...)

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17594

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

   What|Removed |Added

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

--

[Issue 17594] Define DDOC_BLANKLINE as an empty HTML paragraph, thus obviating the need to wrap text in $(P ...)

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17594

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

https://github.com/dlang/dlang.org/commit/1040dd920cf18c7ce0ca2fcde963f90853084cd9
Fix Issue 17594 - Define DDOC_BLANKLINE as an empty HTML paragraph, thus
obviating the need to wrap text in $(P ...)

https://github.com/dlang/dlang.org/commit/a54adeca33341dd92cf090160e19a6a100f6a652
Merge pull request #1795 from andralex/DDOC_BLANKLINE

Fix Issue 17594 - Define DDOC_BLANKLINE as an empty HTML paragraph, t…
merged-on-behalf-of: Andrei Alexandrescu 

--

[Issue 17596] New: dmd d 2.073.2 and 2.074.1 interim generated dmd segfaults on FreeBSD 12-CURRENT

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17596

  Issue ID: 17596
   Summary: dmd d 2.073.2 and 2.074.1 interim generated dmd
segfaults on FreeBSD 12-CURRENT
   Product: D
   Version: D2
  Hardware: x86_64
OS: FreeBSD
Status: NEW
  Severity: major
  Priority: P1
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: c...@freebsd.org

As of r318736, FreeBSD 12-CURRENT (upcoming release) implemented 64-bit inodes.
Since r318736 DMD=../dmd/generated/freebsd/release/64/dmd segfaults with a
corrupted stack. The definitions stat_t and dirent_t have changed.

Initial panic occurs at line 97 of dmd/src/root/file.d.

--

[Issue 17482] [REG 2.074] comile error: Comparing Nullable!Variant with basic type

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17482

--- Comment #4 from Jonathan M Davis  ---
https://github.com/dlang/phobos/pull/5541

--

[Issue 17595] Fix warnings in PDF build & fail on specific warnings in the future

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17595

Vladimir Panteleev  changed:

   What|Removed |Added

 CC||dlang-bugzilla@thecybershad
   ||ow.net

--

[Issue 17593] __POS__ magical constant like __FILE__ and friends

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17593

Vladimir Panteleev  changed:

   What|Removed |Added

 CC||dlang-bugzilla@thecybershad
   ||ow.net

--- Comment #1 from Vladimir Panteleev  ---
I think such an enhancement could use some more background.

When would you find it useful, and how are the existing tools insufficient to
warrant a change in the language?

Right now, you can use:

- string mixins, i.e.:
Pos pos = mixin(mixPos);
  where
enum mixPos = q{ Pos(__FILE__, __MODULE__, __LINE__) };

- The property of __FILE__/__LINE__ etc. that as default arguments, they are
evaluated at the call site:
Pos pos = getPos();
  where
Pos getPos(string f=__FILE__, string m=__MODULE__, int l=__LINE__)
{ return Pos(f, m, l); }

- As above, but also for template arguments, not just runtime function
arguments:
Pos pos = currentPos!();
  where
enum Pos currentPos(string f=__FILE__, string m=__MODULE__, int l=__LINE__)
= Pos(f, m, l);

(I haven't tested the above, but I think they should work.)

--

[Issue 17592] destroy isn't marked @nogc when the class destructor is marked as @nogc

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17592

Vladimir Panteleev  changed:

   What|Removed |Added

   Hardware|x86_64  |All
 OS|Windows |All

--

[Issue 17539] std.parallellism.parallel triggers 'statement not reachable' warnings in the rdmd_test suite

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17539

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

   What|Removed |Added

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

--

[Issue 17539] std.parallellism.parallel triggers 'statement not reachable' warnings in the rdmd_test suite

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17539

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

https://github.com/dlang/phobos/commit/f3770ba1d675ed952012cbfc8dd38b823e1d3ca7
Fix Issue 17539 - std.parallellism.parallel triggers 'statement not reachable'

https://github.com/dlang/phobos/commit/c0652345e992a312d3df2005f56e1b9b7eb1e8c3
Merge pull request #5502 from wilzbach/fix-17539

Fix Issue 17539 - std.parallellism.parallel triggers 'statement not reachable'
merged-on-behalf-of: Vladimir Panteleev 

--

[Issue 17595] New: Fix warnings in PDF build & fail on specific warnings in the future

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17595

  Issue ID: 17595
   Summary: Fix warnings in PDF build & fail on specific warnings
in the future
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: dlang.org
  Assignee: nob...@puremagic.com
  Reporter: greensunn...@gmail.com

There are a lot of warnings in the spec build. At least for the undefined
references  it might make sense to fix them and check for these errors in the
future.


LaTeX Warning: No \author given.
...
LaTeX Warning: Hyper reference `source_text' on page 7 undefined on input line 
197.

[7] (/usr/share/texlive/texmf-dist/tex/latex/base/t1cmtt.fd)

LaTeX Warning: Hyper reference `character_set' on page 8 undefined on input lin
e 261.


LaTeX Warning: Hyper reference `end_of_file' on page 8 undefined on input line 
269.


LaTeX Warning: Hyper reference `end_of_line' on page 8 undefined on input line 
280.

[8]

LaTeX Warning: Hyper reference `white_space' on page 9 undefined on input line 
295.


LaTeX Warning: Hyper reference `comment' on page 9 undefined on input line 311.


[9]

LaTeX Warning: Hyper reference `tokens' on page 10 undefined on input line 372.


[10] [11]
Overfull \hbox (5.318pt too wide) in paragraph at lines 378--378
[]\T1/cmtt/m/it/10.95 CharacterLiteral[] 

LaTeX Warning: Hyper reference `identifiers' on page 12 undefined on input line
 449.

[12]

LaTeX Warning: Hyper reference `string_literals' on page 13 undefined on input 
line 481.

[13] [14] [15] [16]
Underfull \vbox (badness 1028) has occurred while \output is active [17]
[18]
Overfull \hbox (569.97498pt too wide) in paragraph at lines 780--815
 [][] 

LaTeX Warning: Hyper reference `characterliteral' on page 19 undefined on input
 line 818.


LaTeX Warning: Hyper reference `integerliteral' on page 19 undefined on input l
ine 833.

[19] [20] [21] [22]

LaTeX Warning: Hyper reference `binary-literals' on page 23 undefined on input 
line 972.

[23]

LaTeX Warning: Hyper reference `floatliteral' on page 24 undefined on input lin
e 1035.

[24] [25] [26]

LaTeX Warning: Hyper reference `keywords Keywords' on page 27 undefined on inpu
t line 1180.

[27]
Underfull \hbox (badness 1) in paragraph at lines 1216--1216
[][][][][]

Overfull \hbox (7.34686pt too wide) in paragraph at lines 1232--1232
[][][][][]

Underfull \hbox (badness 1) in paragraph at lines 1289--1289
[][][][][]

Underfull \hbox (badness 1) in paragraph at lines 1303--1303
[][][][][]
[28]
Overfull \hbox (24.32198pt too wide) in paragraph at lines 1310--1310
[][][][][]

Overfull \hbox (29.98035pt too wide) in paragraph at lines 1314--1314
[][][][][]

LaTeX Warning: Hyper reference `global_symbols' on page 29 undefined on input l
ine 1323.


Underfull \hbox (badness 1) in paragraph at lines 1329--1329
[][][][]

Overfull \hbox (69.83514pt too wide) in paragraph at lines 1329--1329
[][] \T1/cmtt/m/n/10.95 (alias to immutable(char)[])[] 

Underfull \hbox (badness 1) in paragraph at lines 1330--1330
[][][][]

Overfull \hbox (75.49352pt too wide) in paragraph at lines 1330--1330
[][] \T1/cmtt/m/n/10.95 (alias to immutable(wchar)[])[] 

Underfull \hbox (badness 1) in paragraph at lines 1331--1331
[][][][]

Overfull \hbox (75.49352pt too wide) in paragraph at lines 1331--1331
[][] \T1/cmtt/m/n/10.95 (alias to immutable(dchar)[])[] 

LaTeX Warning: Hyper reference `specialtokens' on page 29 undefined on input li
ne 1338.


LaTeX Warning: Hyper reference `special-token-sequence' on page 29 undefined on
 input line 1361.

[29] [30]

LaTeX Warning: Hyper reference `type' on page 31 undefined on input line 1414.

[31] [32]

LaTeX Warning: Hyper reference `expression' on page 33 undefined on input line 
1491.

[33] [34] [35] [36]
Overfull \hbox (61.25948pt too wide) in paragraph at lines 1694--1694
[][][][][][][][] \T1/cmtt/m/it/10.95 AllocatorArguments$[]$ [][][][][][][] 
ClassArguments$[]$ SuperClass$[]$ Interfaces$[]$ AggregateBody[] 
[37] [38] [39] [40] [41] [42]

LaTeX Warning: Hyper reference `statement' on page 43 undefined on input line 1
976.

[43] [44] [45] [46] [47] [48] [49] [50]

LaTeX Warning: Hyper reference `iasm' on page 51 undefined on input line 2304.

[51] [52] [53] [54] [55]

LaTeX Warning: Hyper reference `declaration' on page 56 undefined on input line
 2488.

[56] [57] [58] [59] [60]

LaTeX Warning: Hyper reference `function' on page 61 undefined on input line 26
67.

[61] [62]
Overfull \hbox (3.78221pt too wide) in paragraph at lines 2769--2769
[][][][][][][][] \T1/cmtt/m/it/10.95 TemplateParameters Parameters MemberFu
nctionAttributes$[]$ Constraint$[]$ [][][]

Overfull \hbox (58.33705pt too wide) in paragraph at lines 2770--2770
[][][][][][][][] \T1/cmtt/m/it/10.95 TemplateParameters Parameters MemberFu
nctionAttributes$[]$

[Issue 9731] Ddoc should output per-paragraph macro instead of $(DDOC_BLANKLINE)

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=9731

--- Comment #7 from github-bugzi...@puremagic.com ---
Commit pushed to master at https://github.com/dlang/dmd

https://github.com/dlang/dmd/commit/f197169c5a573a3dcef72fac503a35b724775082
Fix Issue 9731 - Ddoc should output per-paragraph macro instead of
$(DDOC_BLANKLINE)

--

[Issue 2060] some ddoc design typos

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=2060
Issue 2060 depends on issue 9731, which changed state.

Issue 9731 Summary: Ddoc should output per-paragraph macro instead of 
$(DDOC_BLANKLINE)
https://issues.dlang.org/show_bug.cgi?id=9731

   What|Removed |Added

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

--

[Issue 9731] Ddoc should output per-paragraph macro instead of $(DDOC_BLANKLINE)

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=9731

Andrei Alexandrescu  changed:

   What|Removed |Added

 CC||and...@erdani.com

--- Comment #6 from Andrei Alexandrescu  ---
Related: https://issues.dlang.org/show_bug.cgi?id=17594

https://github.com/dlang/dmd/pull/5344 and
https://github.com/dlang/dlang.org/pull/1795 fix this issue, albeit somewhat
differently than requested.

--

[Issue 17594] Define DDOC_BLANKLINE as an empty HTML paragraph, thus obviating the need to wrap text in $(P ...)

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17594

--- Comment #1 from Andrei Alexandrescu  ---
Related: https://issues.dlang.org/show_bug.cgi?id=9731

--

[Issue 17594] New: Define DDOC_BLANKLINE as an empty HTML paragraph, thus obviating the need to wrap text in $(P ...)

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17594

  Issue ID: 17594
   Summary: Define DDOC_BLANKLINE as an empty HTML paragraph, thus
obviating the need to wrap text in $(P ...)
   Product: D
   Version: D2
  Hardware: All
OS: All
Status: NEW
  Severity: enhancement
  Priority: P1
 Component: dlang.org
  Assignee: nob...@puremagic.com
  Reporter: and...@erdani.com

Currently working on the site's *.dd files is unnecessarily clumsy because of
the requirement that every paragraph is wrapped in $(P ...).

https://github.com/dlang/dmd/pull/5344 fixes the generation part of it by
inserting a $(DDOC_BLANKLINE) whenever there are empty lines in the source.
There is a need for an appropriate definition of DDOC_BLANKLINE for separating
paragraphs so that wrapping text in $(P ...) is not necessary.

--

[Issue 17587] JSONOptions: No forward slash encoding

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17587

--- Comment #2 from Andre  ---
In my AWS SDK I had the issue that \/ was not accepted while passing the JSON
as console argument to the AWS console client. In the meantime I save the JSON
as file and pass the file name to the AWS console client. Here the \/ is
accepted quite fine.
I tried to reactive the old behavior but wasn't able, because passing JSON as
console argument is quite another beast...

My other use cases is purely optical. In an http server I generate JSON
documents on the fly which are outputed to the browser. One example is an
ODATA2 server framework. 
Something similiar to this one
http://services.odata.org/V2/Northwind/Northwind.svc/Customers?$FORMAT=JSON

With the right Chrome plugin, the links are clickable but I have to replace \/
in http://...

--

[Issue 16992] fromISOString, fromISOExtString, and fromSimpleString do not have examples

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

--- Comment #7 from RazvanN  ---
I think that having all fromISOString overloads gathered in a single template
function which is called fromISOString!Choose_type(some_string), where
Choose_type is one of {Date, DateTime, TimeOfDay} is more elegant and the
documentation can be presented a single time; rather than having 3
fromISOString functions dispersed through the documentation.

--

[Issue 16992] fromISOString, fromISOExtString, and fromSimpleString do not have examples

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

--- Comment #6 from Vladimir Panteleev  ---
(In reply to RazvanN from comment #5)
> For now we could wrap the static call in a public call outside the struct
> and generate documentation for that function (and other overloads).

Why not fix the compiler?

--

[Issue 16992] fromISOString, fromISOExtString, and fromSimpleString do not have examples

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

--- Comment #5 from RazvanN  ---
For now we could wrap the static call in a public call outside the struct and
generate documentation for that function (and other overloads).

--

[Issue 16992] fromISOString, fromISOExtString, and fromSimpleString do not have examples

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

--- Comment #3 from Andrei Alexandrescu  ---
The examples to appear in ddox, see e.g.
https://dlang.org/library/std/datetime/date.from_iso_string.html. The problem
is therefore in ddmd/src/doc.d. Probably the intent was to not generate
examples for module-level static functions because those are not accessible
publicly anyway.

--

[Issue 16992] fromISOString, fromISOExtString, and fromSimpleString do not have examples

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

--- Comment #4 from Andrei Alexandrescu  ---
s/to appear/do appear/

--

[Issue 16992] fromISOString, fromISOExtString, and fromSimpleString do not have examples

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=16992

RazvanN  changed:

   What|Removed |Added

 CC||razvan.nitu1...@gmail.com

--- Comment #2 from RazvanN  ---
It seems that the documentation builder has a problem with static methods.
After erasing the static keyword from one method, the documentation appeared as
usual. From what I've seen in phobos, static methods usually do no have
examples.

--

[Issue 17593] New: __POS__ magical constant like __FILE__ and friends

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17593

  Issue ID: 17593
   Summary: __POS__ magical constant like __FILE__ and friends
   Product: D
   Version: D2
  Hardware: All
   URL: http://dlang.org/
OS: All
Status: NEW
  Severity: enhancement
  Priority: P3
 Component: dmd
  Assignee: nob...@puremagic.com
  Reporter: e...@weka.io

Add __POS__ as a more concise (__FILE__, __MODULE__, __LINE__).

Add a "struct Pos { string file, module; size_t line; }" in a core library
somewhere.

Add a __POS__ magical constant that evaluates to Pos(__FILE__, __MODULE__,
__LINE__) but is evaluated at the correct position (equivalent to manually
placing __FILE__, __MODULE__, __LINE__ into separate compile-time variables.

--

[Issue 17590] Unnecessary GC alloc on returning static local struct

2017-07-04 Thread via Digitalmars-d-bugs 
https://issues.dlang.org/show_bug.cgi?id=17590

Tomer Filiba (weka)  changed:

   What|Removed |Added

 CC||to...@weka.io

--