[Issue 7016] local import does not create -deps dependency

https://issues.dlang.org/show_bug.cgi?id=7016 --- Comment #18 from Vladimir Panteleev --- (In reply to RazvanN from comment #17) > Cannot reproduce on Ubuntu 16.04, latest version of compiler. Hopefully I > will try on a windows machine when I get the chance What have

[Issue 7016] local import does not create -deps dependency

https://issues.dlang.org/show_bug.cgi?id=7016 --- Comment #17 from RazvanN --- Cannot reproduce on Ubuntu 16.04, latest version of compiler. Hopefully I will try on a windows machine when I get the chance --

Re: DIP10005: Dependency-Carrying Declarations is now available for community feedback

On 12/20/2016 11:32 PM, Joakim wrote: On Tuesday, 20 December 2016 at 20:51:54 UTC, Andrei Alexandrescu wrote: Thanks for this analysis of the remaining dependency graph, it is worth looking at. Allow me to poke some holes in it. To begin with, the amount of scoping that has been done is

Re: returning struct, destructor

On Wednesday, 21 December 2016 at 14:15:06 UTC, John C wrote: On Wednesday, 21 December 2016 at 11:45:18 UTC, Eugene Wissner wrote: This prints 3 times "Destruct" with dmd 0.072.1. If I remove the if block, it prints "Destruct" only 2 times - the behavior I'm expecting. Why? Possibly to do

Re: Red Hat's issues in considering the D language

On Wednesday, 21 December 2016 at 13:26:14 UTC, ixid wrote: On Tuesday, 20 December 2016 at 23:08:28 UTC, Andrei Alexandrescu wrote: Hello, a few engineers at Red Hat are taking a look at using the D language on the desktop and have reached out to us. They have created a list of issues. We are

Re: D future ...

On Wednesday, 21 December 2016 at 14:50:31 UTC, thedeemon wrote: On Wednesday, 21 December 2016 at 11:54:35 UTC, Ilya Yaroshenko wrote: On Wednesday, 21 December 2016 at 11:36:14 UTC, thedeemon wrote: [...] If this is true, a blog post about it with more details is very welcome --Ilya

Re: D future ...

On Wednesday, 21 December 2016 at 11:54:35 UTC, Ilya Yaroshenko wrote: On Wednesday, 21 December 2016 at 11:36:14 UTC, thedeemon wrote: On Tuesday, 20 December 2016 at 10:18:12 UTC, Kelly Sommers wrote: [...] Bad news: without complete redesign of the language and turning into one more

Re: returning struct, destructor

On Wednesday, 21 December 2016 at 14:15:06 UTC, John C wrote: On Wednesday, 21 December 2016 at 11:45:18 UTC, Eugene Wissner wrote: This prints 3 times "Destruct" with dmd 0.072.1. If I remove the if block, it prints "Destruct" only 2 times - the behavior I'm expecting. Why? Possibly to do

Re: D future ...

On Tuesday, 20 December 2016 at 16:22:43 UTC, Walter Bright wrote: D is quite a bit less formal, but still, if you want action consider that you aren't going to get it with any organization unless you're willing to: 1. pay others to do it 2. convince others that your important issues are

Re: returning struct, destructor

On Wednesday, 21 December 2016 at 11:45:18 UTC, Eugene Wissner wrote: This prints 3 times "Destruct" with dmd 0.072.1. If I remove the if block, it prints "Destruct" only 2 times - the behavior I'm expecting. Why? Possibly to do with named return value optimisation.

Re: Red Hat's issues in considering the D language

On Wednesday, 21 December 2016 at 13:18:48 UTC, Andrei Alexandrescu wrote: On 12/20/16 6:08 PM, Andrei Alexandrescu wrote: Hello, a few engineers at Red Hat are taking a look at using the D language on the desktop and have reached out to us. They have created a list of issues. We are on the

Re: Red Hat's issues in considering the D language

On Tuesday, 20 December 2016 at 23:08:28 UTC, Andrei Alexandrescu wrote: Hello, a few engineers at Red Hat are taking a look at using the D language on the desktop and have reached out to us. They have created a list of issues. We are on the top-level ones, and of course would appreciate any

Re: Red Hat's issues in considering the D language

On 12/20/16 6:08 PM, Andrei Alexandrescu wrote: Hello, a few engineers at Red Hat are taking a look at using the D language on the desktop and have reached out to us. They have created a list of issues. We are on the top-level ones, and of course would appreciate any community help as well.

Re: returning struct, destructor

On Wednesday, 21 December 2016 at 12:32:51 UTC, Nicholas Wilson wrote: On Wednesday, 21 December 2016 at 11:45:18 UTC, Eugene Wissner wrote: Consider we have a function that returns a struct. So for example: import std.stdio; struct A { ~this() { writeln("Destruct"); } } A

Re: Socket missing option: SO_REUSEPORT

On Wednesday, 21 December 2016 at 13:01:53 UTC, Benjiro wrote: I don't think this needs weeks of discussion ;) No discussion needed at all. You could simply file an issue here: https://issues.dlang.org/, or submit a PR.

[Issue 16653] ParameterDefaultValueTuple fails to compile when function has lazy param

https://issues.dlang.org/show_bug.cgi?id=16653 --- Comment #3 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/48398dbd0f42d258461332b619939e550be430de fix issue 16653

[Issue 16653] ParameterDefaultValueTuple fails to compile when function has lazy param

https://issues.dlang.org/show_bug.cgi?id=16653 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

Socket missing option: SO_REUSEPORT

Just check the socket code and there is a small feature missing: enum SocketOption: int { DEBUG =SO_DEBUG,/// Record debugging information BROADCAST =SO_BROADCAST,/// Allow transmission of broadcast messages REUSEADDR =

Re: returning struct, destructor

On Wednesday, 21 December 2016 at 11:45:18 UTC, Eugene Wissner wrote: Consider we have a function that returns a struct. So for example: import std.stdio; struct A { ~this() { writeln("Destruct"); } } A myFunc() { auto a = A(), b = A(); if (false) { return a;

Re: BitArray Slicing

On Wednesday, 21 December 2016 at 12:00:57 UTC, Ezneh wrote: On Wednesday, 21 December 2016 at 11:49:06 UTC, Ilya Yaroshenko wrote: [...] Thanks, I'll check that solution to see if it fits my needs. As an off-topic question, is there any plan in Mir to implement the Tiny Mersenne Twister[1]

Re: BitArray Slicing

On Wednesday, 21 December 2016 at 11:49:06 UTC, Ilya Yaroshenko wrote: On Wednesday, 21 December 2016 at 09:08:51 UTC, Ezneh wrote: Hi, in one of my projects I have to get a slice from a BitArray. I am trying to achieve that like this : void foo(BitArray ba) { auto slice = ba[0..3]; //

Re: D future ...

On Wednesday, 21 December 2016 at 11:54:35 UTC, Ilya Yaroshenko wrote: On Wednesday, 21 December 2016 at 11:36:14 UTC, thedeemon wrote: On Tuesday, 20 December 2016 at 10:18:12 UTC, Kelly Sommers wrote: [...] Bad news: without complete redesign of the language and turning into one more

Re: D future ...

On Wednesday, 21 December 2016 at 11:36:14 UTC, thedeemon wrote: On Tuesday, 20 December 2016 at 10:18:12 UTC, Kelly Sommers wrote: [...] Bad news: without complete redesign of the language and turning into one more C++/CLI (where you have different kinds of pointers in the language for GC

Re: BitArray Slicing

On Wednesday, 21 December 2016 at 09:08:51 UTC, Ezneh wrote: Hi, in one of my projects I have to get a slice from a BitArray. I am trying to achieve that like this : void foo(BitArray ba) { auto slice = ba[0..3]; // Assuming it has more than 4 elements } The problem is that I get an

returning struct, destructor

Consider we have a function that returns a struct. So for example: import std.stdio; struct A { ~this() { writeln("Destruct"); } } A myFunc() { auto a = A(), b = A(); if (false) { return a; } return b; } void main() { myFunc(); } This prints 3

Re: BitArray Slicing

On Wednesday, 21 December 2016 at 09:14:04 UTC, Eugene Wissner wrote: The problem is BitArray keeps multiple elements in one byte. You can't return just three bits but in the best case one byte with 8 elements. What could be done some internal range could be returned that gives access to

Re: D future ...

On Tuesday, 20 December 2016 at 10:18:12 UTC, Kelly Sommers wrote: What I really want is what C++ wanted to deliver but it doesn't. I want something better than writing C but with the same performance as C and the ability to interface with C without the performance loss and with easily

Re: D future ...

On Wednesday, 21 December 2016 at 09:35:31 UTC, Andrey wrote: On Wednesday, 21 December 2016 at 07:47:08 UTC, O-N-S wrote: On Monday, 19 December 2016 at 23:02:59 UTC, Benjiro wrote: I split this from the "Re: A betterC modular standard library?" topic because my response is will be too much

Re: Red Hat's issues in considering the D language

On Tuesday, 20 December 2016 at 23:08:28 UTC, Andrei Alexandrescu wrote: Hello, a few engineers at Red Hat are taking a look at using the D language on the desktop and have reached out to us. They have created a list of issues. We are on the top-level ones, and of course would appreciate any

Re: Improvement in pure functions specification

On 21.12.2016 01:58, Andrei Alexandrescu wrote: On 12/20/16 7:40 PM, Timon Gehr wrote: On 20.12.2016 23:49, Andrei Alexandrescu wrote: https://github.com/dlang/dlang.org/pull/1528 -- Andrei Good, except: "$(P `pure` functions returning `void` will be always called even if it is strongly

Re: D future ...

On Wednesday, 21 December 2016 at 07:47:08 UTC, O-N-S wrote: On Monday, 19 December 2016 at 23:02:59 UTC, Benjiro wrote: I split this from the "Re: A betterC modular standard library?" topic because my response is will be too much off-topic but the whole thread is irking me the wrong way. I

Re: Swap front for char[] input ranges

On Monday, 19 December 2016 at 20:26:26 UTC, Ali Çehreli wrote: On 12/19/2016 06:09 AM, RazvanN wrote: > [...] wrote: >> [...] InputRanges. >> [...] following > [...] char[] > [...] function, so > [...] http://dlang.org/phobos/std_algorithm_mutation.html#bringToFront [...] No need to mention

Re: BitArray Slicing

On Wednesday, 21 December 2016 at 09:08:51 UTC, Ezneh wrote: Hi, in one of my projects I have to get a slice from a BitArray. I am trying to achieve that like this : void foo(BitArray ba) { auto slice = ba[0..3]; // Assuming it has more than 4 elements } The problem is that I get an

BitArray Slicing

Hi, in one of my projects I have to get a slice from a BitArray. I am trying to achieve that like this : void foo(BitArray ba) { auto slice = ba[0..3]; // Assuming it has more than 4 elements } The problem is that I get an error : "no operator [] overload for type BitArray". Is there any

Re: Red Hat's issues in considering the D language

On Tuesday, 20 December 2016 at 23:08:28 UTC, Andrei Alexandrescu wrote: Hello, a few engineers at Red Hat are taking a look at using the D language on the desktop and have reached out to us. They have created a list of issues. We are on the top-level ones, and of course would appreciate any

Spotted on twitter: Packt blog post about some compile-time features of D

https://www.packtpub.com/books/content/modelling-rpg-d/ Maybe worth linking on reddit etc.?

[Issue 16685] template instantiation rejected when passing member of enum struct in value parameter

https://issues.dlang.org/show_bug.cgi?id=16685 bitter.ta...@gmx.com changed: What|Removed |Added CC||bitter.ta...@gmx.com --- Comment #1

About useful assert error information

(Just picking out a random item from the list at [1] and showing the current progress and giving a good point on where to start. Maybe we can do this with the entire list?) The assert statement is "dumb" in a way that it doesn't show me what data it actually compared, making using pure-assert

[Issue 16976] Implicit conversion from ulong to int in foreach_reverse

https://issues.dlang.org/show_bug.cgi?id=16976 bitter.ta...@gmx.com changed: What|Removed |Added CC||bitter.ta...@gmx.com --- Comment #2

<    1   2