On Saturday, 23 November 2019 at 23:21:49 UTC, Nick Sabalausky
(Abscissa) wrote:
On 11/23/19 3:48 PM, Sebastiaan Koppe wrote:
On Saturday, 23 November 2019 at 15:23:41 UTC, Alexandru
Ermicioi wrote:
I was wondering whats your position on Fibers?
I am not going to support them in this
On Sunday, 31 July 2016 at 07:10:46 UTC, cym13 wrote:
On Sunday, 31 July 2016 at 04:55:31 UTC, deadalnix wrote:
On Saturday, 30 July 2016 at 21:42:42 UTC, cym13 wrote:
[...]
That doesn't help. In fact, it makes things worse as now
constructor calls and function call do not have the same
On Tuesday, 7 June 2016 at 11:27:11 UTC, Georgi D wrote:
On Thursday, 2 June 2016 at 08:27:03 UTC, Sönke Ludwig wrote:
[...]
This is great.
Could you look into
https://github.com/rejectedsoftware/vibe.d/issues/1512 ?
It is not a good first impression if the Hello World
application fails
On Thursday, 2 June 2016 at 08:27:03 UTC, Sönke Ludwig wrote:
The release candidate is planned for the 6th, so please take a
moment to test this release. Instead of `dub upgrade
--prerelease`, edit dub.selections.json directly and put
0.7.29-beta.2 as the vibe-d version (there is already an
On Wednesday, 25 May 2016 at 12:19:33 UTC, Steven Schveighoffer
wrote:
On 5/25/16 4:22 AM, Atila Neves wrote:
On Tuesday, 24 May 2016 at 01:29:53 UTC, Steven Schveighoffer
wrote:
Blog post on making Voldemort types without the disk-space
issues:
On Friday, 20 May 2016 at 19:37:23 UTC, Andrei Alexandrescu wrote:
On 5/20/16 2:34 PM, Georgi D wrote:
1) Exponential growth of symbol name with voldemort types.
I like Steven's solution where the compiler lowers the struct
outside of
the method.
Was talking to Walter on the phone and he
On Friday, 20 May 2016 at 16:21:55 UTC, ZombineDev wrote:
On Friday, 20 May 2016 at 13:16:32 UTC, Johan Engelen wrote:
On Friday, 20 May 2016 at 12:57:40 UTC, ZombineDev wrote:
As I said earlier, it would be best if can prevent the
generation of long symbols in the first place, because that
On Thursday, 19 May 2016 at 16:41:59 UTC, Andrei Alexandrescu
wrote:
On 05/19/2016 11:56 AM, Georgi D wrote:
Making a local copy of chain and moving the structure outside
of the
method solved the problem and reduced the code size.
The stripped size even reduced from the version that did not
On Thursday, 19 May 2016 at 12:38:09 UTC, Steven Schveighoffer
wrote:
On 5/17/16 6:04 PM, ZombineDev wrote:
On Tuesday, 17 May 2016 at 21:58:06 UTC, Andrei Alexandrescu
wrote:
On 05/17/2016 05:44 PM, Georgi D wrote:
Hi,
While working on a D project which heavily uses the lazy
algorithms for
On Wednesday, 18 May 2016 at 12:02:13 UTC, Hara Kenji wrote:
On Tuesday, 17 May 2016 at 21:48:55 UTC, Georgi D wrote:
On Friday, 13 May 2016 at 23:31:00 UTC, Timon Gehr wrote:
On 13.05.2016 23:21, Georgi D wrote:
[...]
It's tricky. The reason it fails to compile is that the
template
On Tuesday, 17 May 2016 at 21:58:06 UTC, Andrei Alexandrescu
wrote:
On 05/17/2016 05:44 PM, Georgi D wrote:
Hi,
While working on a D project which heavily uses the lazy
algorithms for
ranges I noticed a sudden huge increase in the compilation
time and the
produced binary size.
[snip]
On Friday, 13 May 2016 at 23:31:00 UTC, Timon Gehr wrote:
On 13.05.2016 23:21, Georgi D wrote:
[...]
It's tricky. The reason it fails to compile is that the
template argument you are passing does not actually refer to
the overload set.
[...]
Should I open a PR in bugzilla for this?
Hi,
While working on a D project which heavily uses the lazy
algorithms for ranges I noticed a sudden huge increase in the
compilation time and the produced binary size.
I chased down the offending change to just a small change in one
line of the code which made the resulting binary to jump
On Monday, 29 February 2016 at 07:54:09 UTC, Sönke Ludwig wrote:
The same procedure will then happen for vibe:http (the new
package will include HTTP/2 support) and the other sub packages.
This is great news. Will the new HTTP package support an endpoint
address and transport abstraction
14 matches
Mail list logo
