On Thu, Aug 7, 2014 at 11:11 AM, Jonathan M Davis via
Digitalmars-d-announce wrote:
> On Thursday, 7 August 2014 at 17:05:29 UTC, Manu via
> Digitalmars-d-announce wrote:
>
>> I've never encountered anybody try and use MSC from the command line in
>> about 15 years professionally.
>>
>
> LOL. Tha
is there a url to download the code samples mentioned in the ebook?
On Sun, Jan 31, 2016 at 5:08 AM, Jacob Carlborg via Digitalmars-d-announce <
digitalmars-d-announce@puremagic.com> wrote:
> On 2016-01-30 19:09, barberian wrote:
>
> I don't know what you're seeing there, but here:
>>
>> Ebook =
found it under https://www.packtpub.com/web-development/d-web-development
On Sat, Feb 6, 2016 at 12:50 AM, Timothee Cour
wrote:
> is there a url to download the code samples mentioned in the ebook?
>
> On Sun, Jan 31, 2016 at 5:08 AM, Jacob Carlborg via Digitalmars-d-announce
> wrote:
>
>> On
no sound :(
On Thu, Jun 23, 2016 at 7:18 PM, Ali Çehreli <
digitalmars-d-announce@puremagic.com> wrote:
> Google Hangout:
>
>
>
> https://hangouts.google.com/hangouts/_/hoaevent/AP36tYciptM-tYpkf-Y0NXXs__5mWY5fBGv_x7TA25cYLo3TZPIe3w?hl=en&authuser=1
>
> Ali
>
>
> On 06/23/2016 01:45 PM, Ali Çehre
is it properly sandboxed / hacking proof?
quick tests:
```
import std.process;
auto msg="sleep 10";
executeShell(msg).output.writeln;
```
correctly results in `Application output (9: Killed)`
"ls -al .." => permission denied
"ls /usr/bin/ld" => -rwxr-xr-x 2 0 0 834648 Jan 3 2013 /usr/bin/l
* -transition=safe/-dip1000
=> not mentioned in http://dlang.org/changelog/2.073.0.html
* std.experimental.ndslice has been deprecated. The synchronization between
Phobos and Mir turned out to be a lot of work with litte gain
=> That's a good move. Will make development faster indeed by not being
>
> * -transition=safe/-dip1000
> => not mentioned in http://dlang.org/changelog/2.073.0.html
>
> That's deliberate, as you can't even use it with writeln yet.
https://issues.dlang.org/show_bug.cgi?id=17090 `dmd -transition=?` needs
quoting => make it `-transition=help`
On Sat, Jan 14, 2017 at 3
could these releases be tied to 'homebrew/linuxbrew' upgrades as part
of release process?
On Sun, Dec 10, 2017 at 10:11 AM, Suliman via Digitalmars-d-announce
wrote:
> On Sunday, 10 December 2017 at 17:33:34 UTC, kinke wrote:
>>
>> Hi everyone,
>>
>> on behalf of the LDC team, I'm glad to announ
that's great... unfortunately
https://github.com/vibe-d/vibe.d/issues/1991 is a regression
preventing from updating to 0.8.X (has a reduced test case). Any help
on this would be very appreciated, thanks!
On Tue, Dec 12, 2017 at 11:44 AM, Sönke Ludwig via
Digitalmars-d-announce wrote:
> The major
thanks @aG0aep6G for this PR https://github.com/dlang/dmd/pull/7841 to fix it.
this should be in point release because:
* ldc2 has correct behavior
* the bug disappears with `-O`
so the argument that ppl would rely on it is moot
On Fri, Feb 2, 2018 at 6:37 AM, Steven Schveighoffer via
Digitalmars
if necessary, to help with transition, one could add a hidden flag
`-log_when_issue_18315_occurred` that would log stacktrace (or maybe
user defined function) when hitting this condition at runtime:
```
void main(){ fun(int.min); }
void fun(int v){ writeln(v>0); }
```
dmd -log_when_issue_18315_oc
so how does one enforce that it imports `bar` as a module and not a
symbol in myModule when doing `import myModule : foo, bar;` ?
could this be supported:
`import myModule : foo, bar :`;
to break ambiguity?
On Tue, Feb 20, 2018 at 12:10 PM, jmh530 via Digitalmars-d-announce
wrote:
> On Tuesday,
you should also mention an important point:
current syntax disallows importing a simple module foo (with no package), eg:
import std.stdio:write,foo; // there's no way to specify a module `foo`
import std.stdio:write & foo; // ok
I don't care whether it's `|` or `&` but `,` as a module separator
IMO this should be the priority:
1. blockers (things that can't be worked around at all or not without
jumping through a lot of hoops)
2. everything else
dmd still doesn't support shared libraries on OSX (cf
https://issues.dlang.org/show_bug.cgi?id=12190)
That prevents a whole category of use ca
the following seems like a easy enough workaround:
just add
` if(this is typeof(this).init) return;` at 1st line of your invariant:
```d
import std.typecons;
import std.range;
struct MyDomainData {
string username;
this(string username) @safe
in(!username.empty)
do { this.us
15 matches
Mail list logo