Easily. When it gives you a merge conflict, you just commit the file generated
from the merge without dealing with the conflicts - or you do try and deal with
the conflicts but you miss one. That sort of thing is caught very easily with
code, because it's not going to compile with all of those
Please report issues with the website at d.puremagic.com/issues
Done. http://d.puremagic.com/issues/show_bug.cgi?id=6335
Also at http://www.d-programming-language.org/phobos/std_getopt.html
I get
Depending on the type of the pointer being bound, getopt recognizes the
following kinds of options:
(OL // <---
Boolean options. These are the simplest options; all they do is set a
Boolean to true:
On 2011-07-14 12:12, Loopback wrote:
> While speaking of the website, how come
> "http://d-programming-language.org/language_reference.html";
> just redirects one instantly to the lexical section?
>
> language-reference.html
>
>
>
> D Runtime Library
>
>
>
>
>
Please report issues with th
While speaking of the website, how come
"http://d-programming-language.org/language_reference.html";
just redirects one instantly to the lexical section?
Yep, that's broken too.
While speaking of the website, how come
"http://d-programming-language.org/language_reference.html";
just redirects one instantly to the lexical section?
language-reference.html
D Runtime Library
On Wednesday 13 July 2011 21:49:00 wrote:
> http://www.d-programming-language.org/statement.html
>
> Scroll down to the bottom. Looks like someone committed a file that had
> merge markup in it. I'm not even sure how git would let you do this.
Easily. When it gives you a merge conflict, you just