Re: Battle-plan for CTFE

On Monday, 19 September 2016 at 10:07:06 UTC, Stefan Koch wrote: Compiling all of phobos does not crash my engine anymore! Great work! Keep up still!

Re: thisExePath purity

On Tuesday, September 20, 2016 04:17:21 crimaniak via Digitalmars-d-learn wrote: > static shared immutable ReturnType!T value; I would point out that immutable is implicitly shared, so there's no reason to put shared on an immutable variable. However, you _do_ want to put shared on a

Re: thisExePath purity

Hi and thanks all! On Tuesday, 20 September 2016 at 00:43:10 UTC, Jonathan M Davis wrote: immutable string executablePath; shared static this() { import std.file : thisExePath(); executablePath = thisExePath(); } This code is good for my needs but I start to think about how to

Re: [WORK] std.file.update function

One way to implement it is to open the existing file as a memory-mapped file. Memory-mapped files only get paged into memory as the memory is referenced. So if you did a memcmp(oldfile, newfile, size), it will stop once the first difference is found, and the rest of the file is never read.

discuss: Comparing Rust and Java or D?

look this article: https://llogiq.github.io/2016/02/28/java-rust.html D language how to compare?

Re: polar coordinates with ggplotd

On Monday, 19 September 2016 at 12:34:56 UTC, Edwin van Leeuwen wrote: On Sunday, 18 September 2016 at 22:13:35 UTC, brocolis wrote: Found an error in ys line. Thanks. Does that mean you solved it? Currently there is no special support for other coordinate systems, but I recently added

Re: thisExePath purity

On Tuesday, September 20, 2016 00:37:10 Stefan Koch via Digitalmars-d-learn wrote: > On Tuesday, 20 September 2016 at 00:01:58 UTC, crimaniak wrote: > > Hi! > > > > Is there situations when output of thisExePath() can be > > different during runtime? If yes, what the reason? > > If no, is this

Re: thisExePath purity

On Tuesday, September 20, 2016 00:01:58 crimaniak via Digitalmars-d-learn wrote: > Hi! > > Is there situations when output of thisExePath() can be different > during runtime? If yes, what the reason? > If no, is this possible to mark it as pure in phobos? > >

Re: thisExePath purity

On 9/19/16 8:01 PM, crimaniak wrote: Hi! Is there situations when output of thisExePath() can be different during runtime? If yes, what the reason? If no, is this possible to mark it as pure in phobos? https://dlang.org/library/std/file/this_exe_path.html Not in a way that D can ensure

Re: thisExePath purity

On Tuesday, 20 September 2016 at 00:01:58 UTC, crimaniak wrote: Hi! Is there situations when output of thisExePath() can be different during runtime? If yes, what the reason? If no, is this possible to mark it as pure in phobos? https://dlang.org/library/std/file/this_exe_path.html No way

[Issue 16418] dip25 wrong escaping reference to this

https://issues.dlang.org/show_bug.cgi?id=16418 --- Comment #2 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/21d65b6a23d8176c9479fb957f5d317916186de8 test typecons.Tuple.rename for sucessful no-ops, working

thisExePath purity

Hi! Is there situations when output of thisExePath() can be different during runtime? If yes, what the reason? If no, is this possible to mark it as pure in phobos? https://dlang.org/library/std/file/this_exe_path.html

[Issue 16513] New: Speed up TemplateInstance.findExistingInstance, hash by mangling

https://issues.dlang.org/show_bug.cgi?id=16513 Issue ID: 16513 Summary: Speed up TemplateInstance.findExistingInstance, hash by mangling Product: D Version: D2 Hardware: All OS: All Status: NEW

[Issue 15907] Unjustified "is not visible from module" deprecation warning when using getMember trait

https://issues.dlang.org/show_bug.cgi?id=15907 --- Comment #11 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/f899b4b59620e354b6ba0acfe843efb559202cd8 fix Issue 15907 - unjustified deprecation with getMember

[Issue 16085] wrong visibility warning for overloaded alias symbol

https://issues.dlang.org/show_bug.cgi?id=16085 --- Comment #14 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/22dc48171eaa3ef43dbec3e6bab6ea7fcb839a37 fix Issue 16085 - wrong visibility warning for overloaded

[Issue 16348] [REG 2.070.2] ICE with package visibility

https://issues.dlang.org/show_bug.cgi?id=16348 --- Comment #5 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/93c3dcf26f5c5ae612ccce044012d2b297fe46bf fix Issue 16348 - ICE with package visibility

[Issue 15780] [REG2.069] CTFE foreach fails with tuple

https://issues.dlang.org/show_bug.cgi?id=15780 --- Comment #5 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/60390bd21a45479b6377751fef4be40159effe0a fix Issue 15780 - [REG2.069] CTFE foreach fails with tuple

Re: Default Template Instantiation

On Monday, 19 September 2016 at 22:17:34 UTC, Mathias Lang wrote: 2016-09-19 23:18 GMT+02:00 Jonathan Marler via Digitalmars-d < digitalmars-d@puremagic.com>: [...] No you can't. The example is wrong, but Stefan is right. Consider: ``` template Foo (T = string) { } template

Re: Default Template Instantiation

On Monday, 19 September 2016 at 22:17:34 UTC, Mathias Lang wrote: No you can't. The example is wrong, but Stefan is right. Try it. It got fixed a few versions ago. Maybe it's broken again ? I remember it working with 2.068

Re: What blogs about D do you read?

On Monday, 19 September 2016 at 21:49:04 UTC, Ali Çehreli wrote: https://atilanevesoncode.wordpress.com/ Ali Thanks, Ali.

Re: Default Template Instantiation

2016-09-19 23:18 GMT+02:00 Jonathan Marler via Digitalmars-d < digitalmars-d@puremagic.com>: > On Monday, 19 September 2016 at 21:14:38 UTC, Stefan Koch wrote: > >> On Monday, 19 September 2016 at 21:09:37 UTC, Jonathan Marler wrote: >> >>> >>> I don't know if I would call this a "destabalizing"

Re: [OT] Brokerage for the D Language Foundation

On 9/19/2016 10:44 AM, Laeeth Isharc wrote: [...] Thanks for taking the time to post this stuff - it's good reading. Stuff I didn't know.

Incremental obj generation

Hi, The previous thread "[WORK] std.file.update function" http://forum.dlang.org/thread/nrmb6b$2lc9$1...@digitalmars.com quickly turned out to be a misnomer after a few posts about object-file-formats and codegen. Therefore I am opening this one. Of course I do have something to say about

Re: What blogs about D do you read?

On 09/19/2016 01:20 PM, Guillaume Piolat wrote: On Monday, 19 September 2016 at 17:42:51 UTC, A D dev wrote: Hi list, What blogs about D do you read? Thanks in advance. https://dlang.org/blog/ http://dblog.aldacron.net/ http://minas-mina.com/ http://nomad.so/tag/d/

Re: Default Template Instantiation

On Monday, 19 September 2016 at 21:14:38 UTC, Stefan Koch wrote: On Monday, 19 September 2016 at 21:09:37 UTC, Jonathan Marler wrote: I don't know if I would call this a "destabalizing" language change though. It should be backwards compatible with the existing semantics. It adds an extra

Re: [WORK] std.file.update function

On 9/19/2016 7:04 AM, Andrei Alexandrescu wrote: On 09/19/2016 01:16 AM, Walter Bright wrote: The compiler currently creates the complete object file in a buffer, then writes the buffer to a file in one command. The reason is mostly because the object file format isn't incremental, the

Re: Default Template Instantiation

On Monday, 19 September 2016 at 21:09:37 UTC, Jonathan Marler wrote: I don't know if I would call this a "destabalizing" language change though. It should be backwards compatible with the existing semantics. It adds an extra step to type deduction, but this would be the very last step of

Re: Default Template Instantiation

On Monday, 19 September 2016 at 20:47:00 UTC, Stefan Koch wrote: On Monday, 19 September 2016 at 20:21:30 UTC, Jonathan Marler wrote: Yes that's why the template cannot deduce the parameters. The question is, when the parameters cannot be deduced, and they are all optional, would it be

Re: What exactly does the compiler switch -betterC do?

On Monday, 20 June 2016 at 06:35:32 UTC, Jacob Carlborg wrote: On 2016-06-19 21:53, Gary Willoughby wrote: When compiling, what exactly does the -betterC flag do? The command help says "omit generating some runtime information and helper functions" but what does this really mean? Is there any

Re: What blogs about D do you read?

On Monday, 19 September 2016 at 20:20:26 UTC, Guillaume Piolat wrote: https://dlang.org/blog/ http://dblog.aldacron.net/ http://minas-mina.com/ http://nomad.so/tag/d/ http://blog.thecybershadow.net/ https://p0nce.github.io/d-idioms/ (disclaimer: my own) Great, thanks!

Re: consequences of removing semicolons in D like in Python

On 09/17/2016 07:32 AM, Chris Wright wrote: python-style syntax a while back, in the D1 days, though I forget the name of it. http://delight.sourceforge.net/ Ali

Re: Default Template Instantiation

On Monday, 19 September 2016 at 20:21:30 UTC, Jonathan Marler wrote: Yes that's why the template cannot deduce the parameters. The question is, when the parameters cannot be deduced, and they are all optional, would it be reasonable for the compiler to infer that the user intended to use the

Re: consequences of removing semicolons in D like in Python

On Monday, 19 September 2016 at 20:22:00 UTC, Chris wrote: The thing is that there is no way of telling how much D code would break (including the compiler), if semicolons were removed or optional. That's too big of a gamble for a purely aesthetic change. I don't see a reason to make that

Re: consequences of removing semicolons in D like in Python

On Monday, 19 September 2016 at 16:52:10 UTC, bpr wrote: On Saturday, 17 September 2016 at 16:43:13 UTC, Nick Sabalausky wrote: If semicolons are such a terrible drain, there's always JS and Python. For someone who likes D, Nim (http://www.nim-lang.org) would be better a choice for a

Re: Default Template Instantiation

On Monday, 19 September 2016 at 19:53:27 UTC, Basile B. wrote: On Monday, 19 September 2016 at 19:38:37 UTC, Jonathan Marler wrote: If you have a template where: 1) All parameters are optional 2) The parameters cannot be deduced Would it be reasonable to instantiate the template with the

Re: What blogs about D do you read?

On Monday, 19 September 2016 at 17:42:51 UTC, A D dev wrote: Hi list, What blogs about D do you read? Thanks in advance. https://dlang.org/blog/ http://dblog.aldacron.net/ http://minas-mina.com/ http://nomad.so/tag/d/ http://blog.thecybershadow.net/ https://p0nce.github.io/d-idioms/

Re: Replace/Rename DWT forum with GUIs forum?

On Monday, 19 September 2016 at 19:29:45 UTC, Karabuta wrote: +1. Someone once posted a thread about this some time ago. I think using "GUIs" is more useful and representative. +1

Re: The removal of inactive forum groups

On Monday, 19 September 2016 at 09:55:16 UTC, Seb wrote: I tried a reorganization a couple of months ago: https://forum.dlang.org/post/gkunyofqycjkgepjz...@forum.dlang.org It didn't work out, because there are there busy people involved: Walter for the NNTP server, Brad for the mailing list

Re: Default Template Instantiation

On Monday, 19 September 2016 at 19:38:37 UTC, Jonathan Marler wrote: If you have a template where: 1) All parameters are optional 2) The parameters cannot be deduced Would it be reasonable to instantiate the template with the default parameter values? For example: template Foo(string str =

Re: What blogs about D do you read?

On Monday, 19 September 2016 at 19:36:22 UTC, Karabuta wrote: I have one here on Vibe.d for beginners https://laberba.github.io/2016/hello-world-app-with-the-vibe.d-web-framework/ I will be writing more for-beginners blogs in the coming few weeks. Thank you. Will read it.

Default Template Instantiation

If you have a template where: 1) All parameters are optional 2) The parameters cannot be deduced Would it be reasonable to instantiate the template with the default parameter values? For example: template Foo(string str = "some string", T...) { class Foo { // class

Re: What blogs about D do you read?

On Monday, 19 September 2016 at 19:29:25 UTC, A D dev wrote: On Monday, 19 September 2016 at 17:42:51 UTC, A D dev wrote: Hi list, What blogs about D do you read? To be more clear: - what blogs that include posts on D, would you recommend to a D beginner? Thanks. I have one here on

Re: Replace/Rename DWT forum with GUIs forum?

On Sunday, 18 September 2016 at 23:21:26 UTC, Gerald wrote: I would like to suggest that the existing DWT forum be renamed or replaced with a more generic GUIs forum. As far as I can tell, the DWT forum doesn't get much traffic these days and I don't believe any of the current GUI options for

Re: What blogs about D do you read?

On Monday, 19 September 2016 at 17:42:51 UTC, A D dev wrote: Hi list, What blogs about D do you read? To be more clear: - what blogs that include posts on D, would you recommend to a D beginner? Thanks.

[Issue 16512] New: Nullify the argument passed to allocator.dispose

https://issues.dlang.org/show_bug.cgi?id=16512 Issue ID: 16512 Summary: Nullify the argument passed to allocator.dispose Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement

Re: Iterate over two arguments at once

On Monday, 19 September 2016 at 18:10:22 UTC, bachmeier wrote: Suppose I want to iterate over two arrays at once: foreach(v1, v2; [1.5, 2.5, 3.5], [4.5, 5.5, 6.5]) { ... } I have seen a way to do this but cannot remember what it is and cannot find it. Thanks for the replies. This is what

Re: Iterate over two arguments at once

On Monday, 19 September 2016 at 18:10:22 UTC, bachmeier wrote: Suppose I want to iterate over two arrays at once: foreach(v1, v2; [1.5, 2.5, 3.5], [4.5, 5.5, 6.5]) { ... } I have seen a way to do this but cannot remember what it is and cannot find it. range.lockstep:

Re: Iterate over two arguments at once

On 9/19/16 2:10 PM, bachmeier wrote: Suppose I want to iterate over two arrays at once: foreach(v1, v2; [1.5, 2.5, 3.5], [4.5, 5.5, 6.5]) { ... } I have seen a way to do this but cannot remember what it is and cannot find it. http://dlang.org/phobos/std_range.html#.zip -Steve

Re: Iterate over two arguments at once

On Monday, 19 September 2016 at 18:10:22 UTC, bachmeier wrote: Suppose I want to iterate over two arrays at once: foreach(v1, v2; [1.5, 2.5, 3.5], [4.5, 5.5, 6.5]) { ... } I have seen a way to do this but cannot remember what it is and cannot find it. You can use std.range.zip:

Re: Battle-plan for CTFE

On Monday, 19 September 2016 at 18:05:34 UTC, Lurker wrote: Good news anyway! Do you have any preliminary results or goals and expectations that you are going to achieve with your rework? Is it mostly perf/memory improvements, are there any new features that this rework will unlock? Thanks

Re: vibe.d maxRequestSize

On Monday, 19 September 2016 at 17:54:05 UTC, Steven Schveighoffer wrote: On 9/19/16 1:34 PM, Chris wrote: [...] Here is the culprit: https://github.com/rejectedsoftware/vibe.d/blob/0.7.29/source/vibe/http/server.d#L1861 And the definition of MaxHTTPHeaderLineLength is:

Iterate over two arguments at once

Suppose I want to iterate over two arrays at once: foreach(v1, v2; [1.5, 2.5, 3.5], [4.5, 5.5, 6.5]) { ... } I have seen a way to do this but cannot remember what it is and cannot find it.

[Issue 16511] Suspected Win64 release-mode code-gen bug

https://issues.dlang.org/show_bug.cgi?id=16511 --- Comment #2 from Nick Sabalausky --- Got a report of the crash happening with both --build=debug (dub's default) and --build=release. It only crashes with --build=release for me. So not really sure what's going on. In

Re: vibe.d maxRequestSize

On 9/19/16 1:34 PM, Chris wrote: On Monday, 19 September 2016 at 16:55:05 UTC, Steven Schveighoffer wrote: Hm... you don't get a full stack trace? Hard to tell what max_bytes should be, it defaults to ulong.max, so no way you are exhausting that. Without knowing where readUntilSmall is

Re: [OT] Brokerage for the D Language Foundation

On Monday, 19 September 2016 at 02:39:33 UTC, Walter Bright wrote: On 9/18/2016 5:20 PM, Andrei Alexandrescu wrote: Thanks. Well this kinda boils down to a tautology. I remember my wife asked me once "what kind of insurance could protect us against anything"? There isn't one (which is kinda

What blogs about D do you read?

Hi list, What blogs about D do you read? Thanks in advance.

[Issue 16511] Suspected Win64 release-mode code-gen bug

https://issues.dlang.org/show_bug.cgi?id=16511 --- Comment #1 from Nick Sabalausky --- Just for the sake of reference, the original report/conversation is here: https://github.com/Abscissa/libInputVisitor/issues/1 --

Re: vibe.d maxRequestSize

On Monday, 19 September 2016 at 16:55:05 UTC, Steven Schveighoffer wrote: Hm... you don't get a full stack trace? Hard to tell what max_bytes should be, it defaults to ulong.max, so no way you are exhausting that. Without knowing where readUntilSmall is called, it's hard to diagnose.

[Issue 16511] New: Suspected Win64 release-mode code-gen bug

https://issues.dlang.org/show_bug.cgi?id=16511 Issue ID: 16511 Summary: Suspected Win64 release-mode code-gen bug Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: critical

Re: vibe.d maxRequestSize

On 9/19/16 11:59 AM, Chris wrote: On Thursday, 15 September 2016 at 13:26:48 UTC, Steven Schveighoffer wrote: On 9/15/16 9:11 AM, Chris wrote: On Wednesday, 14 September 2016 at 20:23:09 UTC, Steven Schveighoffer wrote: Hm.. I have adjusted this in my project, and it works (set to 50M).

Re: consequences of removing semicolons in D like in Python

On Saturday, 17 September 2016 at 16:43:13 UTC, Nick Sabalausky wrote: If semicolons are such a terrible drain, there's always JS and Python. For someone who likes D, Nim (http://www.nim-lang.org) would be better a choice for a language at the same level with Python like syntax. Changing D

Re: seg fault, now what?

On Saturday, 17 September 2016 at 21:12:08 UTC, Ryan wrote: But I don't have another e-mail address, and it seems a bit much to create a fake e-mail account for a few bug reports. mailmetrash.com :)

Re: Ah, simple solution to unittests inside templates

On Mon, Sep 19, 2016 at 09:02:05AM -0700, H. S. Teoh via Digitalmars-d wrote: > On Sat, Sep 17, 2016 at 01:22:52PM -0400, Andrei Alexandrescu via > Digitalmars-d wrote: > > Recall the discussion a few days ago about unittests inside templates > > being instantiated with the template. Often that's

Re: Ah, simple solution to unittests inside templates

On Sat, Sep 17, 2016 at 01:22:52PM -0400, Andrei Alexandrescu via Digitalmars-d wrote: > Recall the discussion a few days ago about unittests inside templates > being instantiated with the template. Often that's desirable, but > sometimes not - for example when you want to generate nice ddoc >

Re: consequences of removing semicolons in D like in Python

On Monday, 19 September 2016 at 15:13:10 UTC, Chris Wright wrote: On Mon, 19 Sep 2016 13:06:30 +, pineapple wrote: If you spend enough time writing Python, you will start to run into cases where meaningful whitespace makes it difficult to write readable, functional code. For the most

Re: vibe.d maxRequestSize

On Thursday, 15 September 2016 at 13:26:48 UTC, Steven Schveighoffer wrote: On 9/15/16 9:11 AM, Chris wrote: On Wednesday, 14 September 2016 at 20:23:09 UTC, Steven Schveighoffer wrote: Hm.. I have adjusted this in my project, and it works (set to 50M). Needed it for uploading large

[Issue 16510] New: Request: RSA digital signature validation in phobos

https://issues.dlang.org/show_bug.cgi?id=16510 Issue ID: 16510 Summary: Request: RSA digital signature validation in phobos Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

Re: consequences of removing semicolons in D like in Python

On Mon, 19 Sep 2016 13:06:30 +, pineapple wrote: > If you > spend enough time writing Python, you will start to run into cases where > meaningful whitespace makes it difficult to write readable, functional > code. For the most part, you can wrap a statement in parentheses in lieu of

[Issue 16509] New: DIP25 'return' attribute not documented for functions

https://issues.dlang.org/show_bug.cgi?id=16509 Issue ID: 16509 Summary: DIP25 'return' attribute not documented for functions Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: major

Re: Emplace vs closures

On 9/19/16 10:26 AM, Lodovico Giaretta wrote: On Monday, 19 September 2016 at 14:22:16 UTC, Steven Schveighoffer wrote: On 9/19/16 7:27 AM, Lodovico Giaretta wrote: What I'd like to know: is this usage widespread? Should we forbid it for the sake of security? No. There is no security

Re: seg fault, now what?

On 9/17/16 5:12 PM, Ryan wrote: Is there an alternative to reporting bugs via bugzilla? I tried to open an account, but they recommend not using your main e-mail address because it will be posted to the web for all the spammers to find. But I don't have another e-mail address, and it seems a

Re: Emplace vs closures

On Monday, 19 September 2016 at 14:22:16 UTC, Steven Schveighoffer wrote: On 9/19/16 7:27 AM, Lodovico Giaretta wrote: What I'd like to know: is this usage widespread? Should we forbid it for the sake of security? No. There is no security concern here. You are dereferencing a null pointer,

Re: Emplace vs closures

On 9/19/16 7:27 AM, Lodovico Giaretta wrote: What I'd like to know: is this usage widespread? Should we forbid it for the sake of security? No. There is no security concern here. You are dereferencing a null pointer, which is perfectly safe. -Steve

Re: [WORK] std.file.update function

On Monday, 19 September 2016 at 14:04:03 UTC, Andrei Alexandrescu wrote: Interesting. What happens e.g. if one makes a change to a function whose generated code is somewhere in the middle of the object file? If it doesn't alter the call graph, doesn't the new .o file share a common prefix

Re: [WORK] std.file.update function

On 09/18/2016 10:05 PM, Brad Roberts via Digitalmars-d wrote: This is nice in the case of no changes, but problematic in the case of some changes. The standard write new, rename technique never has either file in a half-right state. The file is atomically either old or new and nothing in

Re: [WORK] std.file.update function

On 09/19/2016 01:16 AM, Walter Bright wrote: On 9/18/2016 8:20 AM, Andrei Alexandrescu wrote: On 09/18/2016 11:17 AM, Andrei Alexandrescu wrote: Simplest case is - source file is being changed, therefore a new object file is being produced, therefore a new executable is being produced.

Re: [WORK] std.file.update function

On Monday, 19 September 2016 at 06:53:47 UTC, Walter Bright wrote: Doing a linker inside DMD means that object files imported from other C/C++ compilers have to be correctly interpreted. I could do it, but I couldn't do that and continue to work on D. yeah. there is a reason for absense of

Re: Emplace vs closures

On 09/19/2016 02:55 PM, Timon Gehr wrote: This works: import std.stdio; void main(){ int x=3; enum l=()=>x; writeln(x); } I.e. l has the correct runtime context even though it is a static value. Enums are a special kind of static value, though. Can't do that with `static` instead

Re: Forum for new programmers in spanish.

On Monday, 19 September 2016 at 10:10:18 UTC, Seb wrote: I don't speak Spanish, but I do like your idea of bringing D to more people :) Two ideas: 1) You could help to translate the DLang Tour to Spanish: https://tour.dlang.org https://github.com/dlang-tour/spanish 2) StackOverflow has an

Re: Release 2.071.2

On Monday, 19 September 2016 at 13:08:34 UTC, Martin Nowak wrote: On Monday, 19 September 2016 at 12:26:21 UTC, Jack Stouffer wrote: On a slightly related note, I think it would be a good idea to branch off 2.072 and start beta testing right away, as it's been five months since the last point

Re: Ah, simple solution to unittests inside templates

On 9/18/16 8:14 AM, Andrei Alexandrescu wrote: On 9/18/16 6:00 AM, Jonathan M Davis via Digitalmars-d wrote: Yes. That's DIP 82: http://wiki.dlang.org/DIP82 I need to go over it again and then introduce it into the new DIP process. But I really think that that's where we should go to fix this

Re: Emplace vs closures

On Monday, 19 September 2016 at 11:27:03 UTC, Lodovico Giaretta wrote: What I'd like to know: is this usage widespread? Should we forbid it for the sake of security? A big issue I'm finding is that inside most Phobos unittests classes and structs are not marked static even when they could,

Re: Release 2.071.2

On Monday, 19 September 2016 at 12:26:21 UTC, Jack Stouffer wrote: On a slightly related note, I think it would be a good idea to branch off 2.072 and start beta testing right away, as it's been five months since the last point release, and A LOT has changed since then. I fear that we may see

Re: consequences of removing semicolons in D like in Python

On Friday, 16 September 2016 at 23:00:08 UTC, eugene wrote: Hello everyone, what if to remove semicolons at the end of each line of code in D like in Python? Is it worth it? If you write JS in a professional environment, you will almost certainly be required to terminate every line with a

Re: Emplace vs closures

On 19.09.2016 14:35, ag0aep6g wrote: On 09/19/2016 02:24 PM, Lodovico Giaretta wrote: Oh. I didn't thought about that. This means that in the following example, the initialization of `s` is more than a simple call to `S.init`. I was under the impression that in D `S.init` should represent a

Re: Emplace vs closures

On 09/19/2016 02:24 PM, Lodovico Giaretta wrote: Oh. I didn't thought about that. This means that in the following example, the initialization of `s` is more than a simple call to `S.init`. I was under the impression that in D `S.init` should represent a valid state for whatever type `S`.

Re: polar coordinates with ggplotd

On Sunday, 18 September 2016 at 22:13:35 UTC, brocolis wrote: Found an error in ys line. Thanks. Does that mean you solved it? Currently there is no special support for other coordinate systems, but I recently added Guides for x/y coordinates which should make this relatively

Re: Release 2.071.2

On Monday, 19 September 2016 at 11:08:33 UTC, Martin Nowak wrote: Glad to announce D 2.071.2. http://dlang.org/download.html This point release fixes many issues with the new lookup and import rules. It should be used as a stopgap version when updating older code. The deprecations, the old

Re: Emplace vs closures

On Monday, 19 September 2016 at 11:45:25 UTC, ag0aep6g wrote: Note that it would also segfault with `auto ps = S.init;`, and for the same reason: missing context pointer. Oh. I didn't thought about that. This means that in the following example, the initialization of `s` is more than a simple

Re: Emplace vs closures

On 09/19/2016 01:27 PM, Lodovico Giaretta wrote: As we all should know, std.conv.emplace does not play well with closures: void main() { int x = 42; struct S { auto getX() { return x; } } S s; assert(s.getX == x); auto ps = someBuffer.emplace!S();

Emplace vs closures

As we all should know, std.conv.emplace does not play well with closures: void main() { int x = 42; struct S { auto getX() { return x; } } S s; assert(s.getX == x); auto ps = someBuffer.emplace!S(); assert(s.getX == x);// SEGFAULT! } As

[Issue 16405] Trojan Win32/Ipac.B!cl detected on dmd-2.071.1.exe

https://issues.dlang.org/show_bug.cgi?id=16405 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu --- Comment #6

Release 2.071.2

Glad to announce D 2.071.2. http://dlang.org/download.html This point release fixes many issues with the new lookup and import rules. It should be used as a stopgap version when updating older code. The deprecations, the old access checks, and the -transition=import/checkimports switches are

[Issue 16071] Source file path and module name should match exactly

https://issues.dlang.org/show_bug.cgi?id=16071 Mathias Lang changed: What|Removed |Added CC|

Re: consequences of removing semicolons in D like in Python

On Saturday, 17 September 2016 at 14:47:38 UTC, eugene wrote: On Saturday, 17 September 2016 at 14:23:40 UTC, jmh530 wrote: What if the OP wrote a compiler that turned his version of D sans semicolons into proper D code? i didn't try to implement it myself, but i will try There's already a

Re: Forum for new programmers in spanish.

On Monday, 19 September 2016 at 05:56:04 UTC, Geert wrote: Hi all! I'm a PHP programmer, and i've been searching for new languages to learn. I think D it's the best of the newest languages, due its good documentation, clean sintaxis (or less verbose), and the applications developed in D run

Re: Battle-plan for CTFE

On Thursday, 8 September 2016 at 18:54:52 UTC, Stefan Koch wrote: On Thursday, 8 September 2016 at 13:11:23 UTC, Stefan Koch wrote: On Thursday, 8 September 2016 at 10:44:55 UTC, Stefan Koch wrote: compiling parts of phobos does no longer crash the new engine. However it still produces

[Issue 16071] Source file path and module name should match exactly

https://issues.dlang.org/show_bug.cgi?id=16071 Walter Bright changed: What|Removed |Added Status|NEW |RESOLVED

Re: Omitting optional tags

Well, a lot can be done to optimize generated html, e.g. it has a lot of spaces and questionable markup like href='object.html'>object

Re: The removal of inactive forum groups

On Sunday, 18 September 2016 at 13:17:33 UTC, Dennis Ritchie wrote: Hi, all It seems to me that a group of `Beta` should be removed, because the last activity in this group dated November 30, 2015: https://forum.dlang.org/post/565bc28c.8080...@dawg.eu Group `Study` is also not very active, so

  1   2   >