dlangBugzillaToGithub

#### jack (@JackStouffer) commented on 2017-01-19T17:03:46Z ````markdown (In reply to Sophie from comment #1) > I think this is the correct behavior. The empty string is not valid as a...

#### meapineapple commented on 2017-01-19T17:11:38Z ````markdown It's a missing value, but in the case of numeric types a missing value is simply one example of a malformed value. I think...

#### jack (@JackStouffer) commented on 2017-01-19T17:30:21Z ````markdown (In reply to Sophie from comment #3) > It's a missing value, but in the case of numeric types a missing value is...

#### meapineapple commented on 2017-01-19T17:38:41Z ````markdown (In reply to Jack Stouffer from comment #4) > (In reply to Sophie from comment #3) > The problem is, if I just get...

#### jrdemail2000-dlang commented on 2017-01-20T21:09:58Z ````markdown There is no standard behavior for empty fields in CSV. Pragmatically, it's an application level decision, meaning that the application that generated the CSV...

#### bugzilla (@WalterBright) commented on 2019-12-14T12:48:02Z ````markdown While I understand the wish for having defaults for empty statements, I don't think this is a bug. The current implementation just does...

#### sean commented on 2011-05-06T10:56:50Z ````markdown I'll take care of core.demangle. core.sys.* and core.stdc.* are interfaces for C libraries and I'd expect the user to refer to the documentation for...

#### kennytm commented on 2011-05-06T11:21:47Z ````markdown (In reply to comment #1) > I'll take care of core.demangle. core.sys.* and core.stdc.* are interfaces for > C libraries and I'd expect the...

#### doob (@jacob-carlborg) commented on 2011-05-06T11:47:13Z ````markdown How about add an empty doc comment at every declaration making the declarations visible in the documentation. And also add a note that...

#### sean commented on 2011-05-09T15:25:28Z ````markdown The module headers already say which spec they follow. What if I added a hyperlink to the official docs (when available) as well? ````