gdc-6.3.0 on travis borked?

When using gdc-6.3.0 on travis-ci, travis is reporting that it can't download the compiler: -- $ source "$(CURL_USER_AGENT="$CURL_USER_AGENT" bash install.sh gdc-6.3.0 --activate)" curl: (22) The requested URL returned error: 404 Not Found

Re: First Impressions!

On Thursday, 30 November 2017 at 19:37:47 UTC, Steven Schveighoffer wrote: On 11/30/17 1:20 PM, Patrick Schluter wrote: On Thursday, 30 November 2017 at 17:40:08 UTC, Jonathan M Davis wrote: English and thus don't as easily hit the cases where their code is wrong. For better or worse, UTF-16

Re: Template specialisation, "Generic type locking", offline stdlib docs and case-based template question

On Friday, December 01, 2017 03:39:12 helxi via Digitalmars-d-learn wrote: > 1. Template specialisation. > Why is this useful?: > T getResponse(T = int)(string question); And how does it differ > from > int getResponse(string question); ? > > Context: http://ddili.org/ders/d.en/templates.html :

Re: Thoughts about D

On Friday, 1 December 2017 at 03:23:23 UTC, Walter Bright wrote: On 11/30/2017 3:51 PM, Nicholas Wilson wrote: On Thursday, 30 November 2017 at 18:18:41 UTC, Jonathan M Davis wrote: But I have a hard time believing that the cost of assertions relates to constructing an AssertError unless the

Re: Template specialisation, "Generic type locking", offline stdlib docs and case-based template question

On Friday, 1 December 2017 at 03:39:12 UTC, helxi wrote: 1. Template specialisation. Why is this useful?: T getResponse(T = int)(string question); And how does it differ from int getResponse(string question); ? Because you can change the T at the call site. Let me give you a real world

Re: Thoughts about D

On Friday, 1 December 2017 at 04:07:24 UTC, Jonathan M Davis wrote: It only implies no bounds checking in @system code, though obviously, if you're not marking code with @safe or simply want the bounds checking to be enabled in @system code, then using -release isn't something that you're

Re: Thoughts about D

On Friday, 1 December 2017 at 03:52:01 UTC, user1234 wrote: Aren't hardware breakpoints limited in numbers ? I've never heard that and can't think of any reason why it would be. The instruction as far as the CPU is concerned is to just trigger the behavior when it is executed, it doesn't

Re: Thoughts about D

On Friday, December 01, 2017 03:43:07 Adam D. Ruppe via Digitalmars-d wrote: > On Friday, 1 December 2017 at 03:23:23 UTC, Walter Bright wrote: > > 26 bytes of inserted Bloaty McBloatface code and 15 bytes of > > > data. My proposal: > I suggest we break up the -release switch into different

Re: Template specialisation, "Generic type locking", offline stdlib docs and case-based template question

On Friday, 1 December 2017 at 03:39:12 UTC, helxi wrote: 1. Template specialisation. Why is this useful?: T getResponse(T = int)(string question); And how does it differ from int getResponse(string question); ? Good Q. Without thinking more it looks like a pointless example. The only

Re: Thoughts about D

On Friday, 1 December 2017 at 03:43:07 UTC, Adam D. Ruppe wrote: On Friday, 1 December 2017 at 03:23:23 UTC, Walter Bright wrote: 26 bytes of inserted Bloaty McBloatface code and 15 bytes of data. My proposal: [...] int 3, on the other hand, is explicitly for debugging - which is what we want

Re: Thoughts about D

On Friday, 1 December 2017 at 03:23:23 UTC, Walter Bright wrote: 26 bytes of inserted Bloaty McBloatface code and 15 bytes of data. My proposal: I suggest we break up the -release switch into different options. I never, never use -release since it implies no bounds checking. But if we wanted

Template specialisation, "Generic type locking", offline stdlib docs and case-based template question

1. Template specialisation. Why is this useful?: T getResponse(T = int)(string question); And how does it differ from int getResponse(string question); ? Context: http://ddili.org/ders/d.en/templates.html : Section: "Default template parameters" 2. "Generic locking". Is it possible to

Re: Thoughts about D

On 11/30/2017 3:51 PM, Nicholas Wilson wrote: On Thursday, 30 November 2017 at 18:18:41 UTC, Jonathan M Davis wrote: But I have a hard time believing that the cost of assertions relates to constructing an AssertError unless the compiler is inlining a bunch of stuff at the assertion site. If

Re: Silicon Valley D Meetup - November 30, 2017 - "DCompute: Harnessing all your hardware" by Nicholas Wilson

Online now: https://hangouts.google.com/call/dKQWkub93bzfHCBrfDeHAAEM Ali On 11/17/2017 04:04 PM, Ali Çehreli wrote: We're very fortunate to have Nic as our speaker this month. He will be connecting remotely. We will announce the Google Hangouts link later so that you can join as well.

Re: Heads-up: upcoming instabilities in std.experimental.allocator, and what to do

On Thursday, 30 November 2017 at 19:01:02 UTC, Andrei Alexandrescu wrote: Hi all, Eduard, Alexandru Jercaianu and I are working on improving allocators' design and implementation. This entails a few breaking changes. In order to make matters easier for code using allocators, Sebastian

Re: Thoughts about D

On Thu, Nov 30, 2017 at 11:12:58AM -0700, Jonathan M Davis via Digitalmars-d wrote: > On Thursday, November 30, 2017 16:48:10 Adam D. Ruppe via Digitalmars-d > wrote: > > On Thursday, 30 November 2017 at 16:12:04 UTC, H. S. Teoh wrote: > > > Which brings us to the implementation of assert()

[Issue 15290] length of associative array literal with duplicate keys is wrong

https://issues.dlang.org/show_bug.cgi?id=15290 --- Comment #3 from hst...@quickfur.ath.cx --- Another user on the learn forum ran into this too: http://forum.dlang.org/post/awmxcwlvfxmsrfiax...@forum.dlang.org --

Re: using vibe listenHTTP in a library on OSX causes: core.sync.exception.SyncError@(0): Unable to lock mutex.

on OSX 10.13.1 if that matters; IIRC it was working on previous OSX version. On Thu, Nov 30, 2017 at 4:46 PM, Timothee Cour wrote: > I get: core.sync.exception.SyncError@(0): Unable to lock mutex. > when calling listenHTTP via a library. It works when compiling >

Re: associative array: unexpected results after static initialization

Seems like this problem is already known: https://issues.dlang.org/show_bug.cgi?id=15290 Here's the fix: https://github.com/dlang/druntime/pull/1980 --T

[Issue 15290] length of associative array literal with duplicate keys is wrong

https://issues.dlang.org/show_bug.cgi?id=15290 hst...@quickfur.ath.cx changed: What|Removed |Added Keywords||pull CC|

using vibe listenHTTP in a library on OSX causes: core.sync.exception.SyncError@(0): Unable to lock mutex.

I get: core.sync.exception.SyncError@(0): Unable to lock mutex. when calling listenHTTP via a library. It works when compiling everything in a single application without using intermediate library. details: using: dmd:2.077 dub build dmd -ofmain -L-Ldir -L-ltest1 -Isource import/main.d ./main

Re: associative array: unexpected results after static initialization

On Thu, Nov 30, 2017 at 03:57:37PM -0800, H. S. Teoh via Digitalmars-d-learn wrote: > Hmm, which compiler are you using, and which version? I cannot > reproduce this bug with DMD git head. It may be have fixed since the > release you're using? [...] Sorry, I was testing the wrong code. This

Re: associative array: unexpected results after static initialization

Hmm, which compiler are you using, and which version? I cannot reproduce this bug with DMD git head. It may be have fixed since the release you're using? --T

Re: associative array: unexpected results after static initialization

On Thu, Nov 30, 2017 at 11:50:13PM +, kdevel via Digitalmars-d-learn wrote: > This program > > ``` void aa_stat(T, U) (T[U] aa) { import std.stdio; writefln ("aa > : %s", aa); writefln ("aa.length : %d", aa.length); writefln ("aa.keys > : %s", aa.keys); writefln ("aa.values : %s", aa.values);

Re: Thoughts about D

On Thursday, 30 November 2017 at 18:18:41 UTC, Jonathan M Davis wrote: But I have a hard time believing that the cost of assertions relates to constructing an AssertError unless the compiler is inlining a bunch of stuff at the assertion site. If that's what's happening, then it would increase

associative array: unexpected results after static initialization

This program ``` void aa_stat(T, U) (T[U] aa) { import std.stdio; writefln ("aa: %s", aa); writefln ("aa.length : %d", aa.length); writefln ("aa.keys : %s", aa.keys); writefln ("aa.values : %s", aa.values); foreach (k, v; aa) writeln (k, ": ", v); } void main

Re: Attributes on Enum Members: Call for use cases.

On 30.11.2017 15:19, Steven Schveighoffer wrote: On 11/30/17 3:26 AM, Timon Gehr wrote: On 30.11.2017 00:23, Steven Schveighoffer wrote: Looking at std.traits, it looks like we use this mechanism to get everything: int func(int param1) static if(is(typeof(func) F == __parameters)) {

Re: std.algorithm

On Thursday, 30 November 2017 at 21:49:56 UTC, Meta wrote: On Thursday, 30 November 2017 at 20:49:36 UTC, flamencofantasy wrote: [...] This *almost* works: [...] That's what I needed, thanks!

Re: Convert a single element into a range

On Thursday, 30 November 2017 at 22:52:33 UTC, Ali Çehreli wrote: On 11/30/2017 02:47 PM, A Guy With a Question wrote: This is probably a dumb question, but what I did looks ugly. Is there a way (preferably a one liner) to convert a single element, like an int or char or bool, into a range?

Re: Convert a single element into a range

On 11/30/2017 02:47 PM, A Guy With a Question wrote: This is probably a dumb question, but what I did looks ugly. Is there a way (preferably a one liner) to convert a single element, like an int or char or bool, into a range? import std.range; void main() { auto r = only(42); static

Convert a single element into a range

This is probably a dumb question, but what I did looks ugly. Is there a way (preferably a one liner) to convert a single element, like an int or char or bool, into a range?

[Issue 18023] std.net.isemail is copied from code and the license was changed. This must be fixed.

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

Re: Question on Dual-Licensing Some Code for Phobos

On 11/30/2017 1:58 PM, Walter Bright wrote: I checked, and the Phobos module is clearly in violation of the license in https://github.com/dominicsayers/isemail/blob/master/is_email.php This needs to be fixed immediately. https://issues.dlang.org/show_bug.cgi?id=18023 Dominic gave us

[Issue 18023] std.net.isemail is copied from code and the license was changed. This must be fixed.

https://issues.dlang.org/show_bug.cgi?id=18023 --- Comment #1 from Walter Bright --- https://github.com/dlang/phobos/pull/5897 --

Re: Question on Dual-Licensing Some Code for Phobos

On 11/30/2017 11:17 AM, Jack Stouffer wrote: I'm starting work on a proposal for stdx.decimal, and one of the clearest implementations to work off of is the Python implementation. This however, poses a problem because Python's source is under the PSFL, a BSD-like permissive license. Any

[Issue 18023] New: std.net.isemail is copied from code and the license was changed. This must be fixed.

https://issues.dlang.org/show_bug.cgi?id=18023 Issue ID: 18023 Summary: std.net.isemail is copied from code and the license was changed. This must be fixed. Product: D Version: D2 Hardware: All OS: All

Re: First Impressions!

On 11/30/2017 5:22 AM, A Guy With a Question wrote: It's also worth mentioning that the more I think about it, the UTF8 vs. UTF16 thing was probably not worth mentioning with the rest of the things I listed out. It's pretty minor and more of a preference. Both Windows and Java selected UTF16

Re: std.algorithm

On Thursday, 30 November 2017 at 20:49:36 UTC, flamencofantasy wrote: Hello, I have the following csv text; auto input = "Start Date,End Date,Subject,All day event,Categories,Show time as 1/1/2018,1/1/2018,New Year's Day,TRUE,Holiday,3 1/15/2018,1/15/2018,\"Martin Luther King, Jr.

[Issue 17393] AllocatorList leaks memory in "ouroboros mode"

https://issues.dlang.org/show_bug.cgi?id=17393 alex.jercai...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED CC|

Re: Heads-up: upcoming instabilities in std.experimental.allocator, and what to do

On Thursday, 30 November 2017 at 19:01:02 UTC, Andrei Alexandrescu wrote: Hi all, Eduard, Alexandru Jercaianu and I are working on improving allocators' design and implementation. This entails a few breaking changes. [...] Sounds good! Please consider -betterC on your refactoring. Would

std.algorithm

Hello, I have the following csv text; auto input = "Start Date,End Date,Subject,All day event,Categories,Show time as 1/1/2018,1/1/2018,New Year's Day,TRUE,Holiday,3 1/15/2018,1/15/2018,\"Martin Luther King, Jr. Day\",TRUE,Holiday,3 2/19/2018,2/19/2018,President's Day,TRUE,Holiday,3

Re: Question on Dual-Licensing Some Code for Phobos

On Thursday, 30 November 2017 at 19:17:32 UTC, Jack Stouffer wrote: I'm starting work on a proposal for stdx.decimal, and one of the clearest implementations to work off of is the Python implementation. This however, poses a problem because Python's source is under the PSFL, a BSD-like

Re: First Impressions!

On 11/30/17 1:20 PM, Patrick Schluter wrote: On Thursday, 30 November 2017 at 17:40:08 UTC, Jonathan M Davis wrote: English and thus don't as easily hit the cases where their code is wrong. For better or worse, UTF-16 hides it better than UTF-8, but the problem exists in both. To give just

Re: Question on Dual-Licensing Some Code for Phobos

On Thursday, November 30, 2017 19:17:32 Jack Stouffer via Digitalmars-d wrote: > I'm starting work on a proposal for stdx.decimal, and one of the > clearest implementations to work off of is the Python > implementation. > > This however, poses a problem because Python's source is under > the

Re: Thoughts about D

On Thursday, November 30, 2017 19:14:50 Ola Fosheim Grøstad via Digitalmars- d wrote: > On Thursday, 30 November 2017 at 18:10:01 UTC, Jonathan M Davis > > wrote: > > whereas it would have squeaked by in a smaller object, but it's > > really a bug to be calling a member function on a null object >

Question on Dual-Licensing Some Code for Phobos

I'm starting work on a proposal for stdx.decimal, and one of the clearest implementations to work off of is the Python implementation. This however, poses a problem because Python's source is under the PSFL, a BSD-like permissive license. Any derivative work, such as a D conversion, must

Re: std.range.interfaces : InputRange moveFront

On 11/30/2017 07:31 AM, Tony wrote: On Thursday, 30 November 2017 at 09:50:37 UTC, Tony wrote: On Thursday, 30 November 2017 at 09:47:14 UTC, Tony wrote: Thanks for the reply. Probably just missing it, but in poking around dlang.org (Language Reference and Library Reference) I am having

Re: Thoughts about D

On Thursday, 30 November 2017 at 18:10:01 UTC, Jonathan M Davis wrote: whereas it would have squeaked by in a smaller object, but it's really a bug to be calling a member function on a null object anyway. Well, it is a bug, but the member-function may have been written with an invariant in

Re: Chocolatey Packages for DMD, LDC, and GDC

On Thursday, 30 November 2017 at 10:53:02 UTC, Jacob Carlborg wrote: Done: https://github.com/jacob-carlborg/dvm#limitations That's great, thanks!

Re: First Impressions!

On Thursday, November 30, 2017 18:32:46 A Guy With a Question via Digitalmars-d wrote: > On Thursday, 30 November 2017 at 17:56:58 UTC, Jonathan M Davis > > wrote: > > On Thursday, November 30, 2017 03:37:37 Walter Bright via > > Digitalmars-d wrote: > > Language-wise, I think that most of the

Heads-up: upcoming instabilities in std.experimental.allocator, and what to do

Hi all, Eduard, Alexandru Jercaianu and I are working on improving allocators' design and implementation. This entails a few breaking changes. In order to make matters easier for code using allocators, Sebastian Wilzbach created a dub package freezing the existing API:

Re: Private imports and Objects

On Thursday, 30 November 2017 at 06:44:43 UTC, Jonathan M Davis wrote: Object exists primarily because D didn't originally have templates, and when you don't have templates, having a single base class is the only way to have a function accept any class, and for something like a container,

Re: First Impressions!

On Thursday, 30 November 2017 at 17:56:58 UTC, Jonathan M Davis wrote: On Thursday, November 30, 2017 03:37:37 Walter Bright via Digitalmars-d wrote: Language-wise, I think that most of the UTF-16 is driven by the fact that Java went with UCS-2 / UTF-16, and C# followed them (both because they

Re: First Impressions!

On Thursday, 30 November 2017 at 17:56:58 UTC, Jonathan M Davis wrote: On Thursday, November 30, 2017 03:37:37 Walter Bright via Digitalmars-d wrote: On 11/30/2017 2:39 AM, Joakim wrote: > Java, .NET, Qt, Javascript, and a handful of others use > UTF-16 too, some starting off with the earlier

Re: First Impressions!

On Thursday, 30 November 2017 at 17:40:08 UTC, Jonathan M Davis wrote: English and thus don't as easily hit the cases where their code is wrong. For better or worse, UTF-16 hides it better than UTF-8, but the problem exists in both. To give just an example of what can go wrong with UTF-16.

Re: Thoughts about D

On Thursday, November 30, 2017 08:12:04 H. S. Teoh via Digitalmars-d wrote: > But of course, this assumes that we even need to throw AssertError in > the first place. If this can be made optional, we can skip the stack > unwinding code altogether. (But I can see that this will only work for >

Re: First Impressions!

On Thursday, 30 November 2017 at 17:40:08 UTC, Jonathan M Davis wrote: [...] And if you're not dealing with Asian languages, UTF-16 uses up more space than UTF-8. Not even that in most cases. Only if you use unstructured text can it happen that UTF-16 needs less space than UTF-8. In most

Re: Thoughts about D

On Thursday, November 30, 2017 16:48:10 Adam D. Ruppe via Digitalmars-d wrote: > On Thursday, 30 November 2017 at 16:12:04 UTC, H. S. Teoh wrote: > > Which brings us to the implementation of assert() itself. What > > about it makes it so big? I suspect most of the bloat comes > > from throwing

Re: Thoughts about D

On Thursday, November 30, 2017 10:39:07 Ola Fosheim Grøstad via Digitalmars- d wrote: > On Thursday, 30 November 2017 at 09:01:20 UTC, Jonathan M Davis > > wrote: > > It's close enough. Instead of segfaulting when the member > > function is called, it'll segfault when it tries to access one > > of

Re: First Impressions!

On Thursday, November 30, 2017 03:37:37 Walter Bright via Digitalmars-d wrote: > On 11/30/2017 2:39 AM, Joakim wrote: > > Java, .NET, Qt, Javascript, and a handful of others use UTF-16 too, some > > starting off with the earlier UCS-2: > > > > https://en.m.wikipedia.org/wiki/UTF-16#Usage > > > >

Re: Time to move logger from experimental to std ?

On Thursday, 30 November 2017 at 09:37:27 UTC, Robert burner Schadek wrote: On Wednesday, 29 November 2017 at 19:48:44 UTC, Nathan S. wrote: Considering that one of those issues is that the logger outputs garbage when given a wstring or a dstring, I would not take this as an indication that

[Issue 15954] std.experimental.logger repeats wstring message

https://issues.dlang.org/show_bug.cgi?id=15954 Nathan S. changed: What|Removed |Added Status|ASSIGNED|RESOLVED

Re: First Impressions!

On Tuesday, 28 November 2017 at 03:01:33 UTC, A Guy With an Opinion wrote: - Attributes. I had another post in the Learn forum about attributes which was unfortunate. At first I was excited because it seems like on the surface it would help me write better code, but it gets a little tedious

Re: First Impressions!

On Thursday, November 30, 2017 13:18:37 A Guy With a Question via Digitalmars-d wrote: > As long as you understand it's limitations I think most bugs can > be avoided. Where UTF16 breaks down, is pretty well defined. > Also, super rare. I think UTF32 would be great to, but it seems > like just a

Re: Private imports and Objects

On Thursday, November 30, 2017 10:54:44 helxi via Digitalmars-d-learn wrote: > On Thursday, 30 November 2017 at 06:44:43 UTC, Jonathan M Davis > > wrote: > > On Thursday, November 30, 2017 06:29:43 helxi via > > > Digitalmars-d-learn wrote: > [] > > > I don't understand the question. You're asking

Re: First Impressions!

On Tuesday, 28 November 2017 at 03:37:26 UTC, rikki cattermole wrote: Be aware Microsoft is alone in thinking that UTF-16 was awesome. Everybody else standardized on UTF-8 for Unicode. UCS2 was awesome. UTF-16 is used by Java, JavaScript, Objective-C, Swift, Dart and ms tech, which is 28% of

Re: Inference of Scoped Destruction

On Thursday, 30 November 2017 at 16:50:02 UTC, Stefan Koch wrote: On Thursday, 30 November 2017 at 16:31:25 UTC, Nordlöw wrote: Are there any plans to D compilers to use recent DIP-1000 to infer scoped destruction of GC-allocated data such as in the following case: T sum(T)(in T[] x) // x

[Issue 18022] New: DDoc: reduce ddoc has UT between documentation

https://issues.dlang.org/show_bug.cgi?id=18022 Issue ID: 18022 Summary: DDoc: reduce ddoc has UT between documentation Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: enhancement

[Issue 15349] DDoc: comments on function templates are skipped for templates without doc comment

https://issues.dlang.org/show_bug.cgi?id=15349 John Hall changed: What|Removed |Added CC|

Re: Thoughts about D

On Thursday, 30 November 2017 at 16:12:04 UTC, H. S. Teoh wrote: Can you elaborate? As I understand it, DWARF exception handling even on the non-exceptional case, is a bit more expensive than our old way. Not hugely expensive but for dmd where we count milliseconds it might add up. Which

Re: Inference of Scoped Destruction

On Thursday, 30 November 2017 at 16:31:25 UTC, Nordlöw wrote: Are there any plans to D compilers to use recent DIP-1000 to infer scoped destruction of GC-allocated data such as in the following case: T sum(T)(in T[] x) // x cannot escape scope of `sum` { /// calculate and return sum of

Inference of Scoped Destruction

Are there any plans to D compilers to use recent DIP-1000 to infer scoped destruction of GC-allocated data such as in the following case: T sum(T)(in T[] x) // x cannot escape scope of `sum` { /// calculate and return sum of `x` ... } double f(size_t n) { auto x = new int[n]; //

Re: Thoughts about D

On Wed, Nov 29, 2017 at 07:29:56PM -0800, Walter Bright via Digitalmars-d wrote: > On 11/29/2017 7:15 PM, Jonathan M Davis wrote: > > I wouldn't have expected assertions to cost much more than however > > much it costs to evaluate the expression being asserted unless the > > assertion fails. Now,

Re: Instructions to build DMD from source don't work (anymore) here

On 2017-11-30 12:19, Basile B. wrote: That's strange because as said i had g++ / c++ but DMD compiles only once gcc-c++ setup. Anyway, working now. It should be possible to get which package the "g++" file belongs to [1]. [1]

Re: std.range.interfaces : InputRange moveFront

On Thursday, 30 November 2017 at 09:50:37 UTC, Tony wrote: On Thursday, 30 November 2017 at 09:47:14 UTC, Tony wrote: Thanks for the reply. Probably just missing it, but in poking around dlang.org (Language Reference and Library Reference) I am having trouble finding out about the move(),

Re: Release D v2.077.1

On Thursday, 30 November 2017 at 13:52:00 UTC, Martin Nowak wrote: Glad to announce D v2.077.1. http://dlang.org/download.html This point release fixes a few issues over v2.077.1, see the changelog for more details. http://dlang.org/changelog/v2.077.1.html - -Martin Thanks for all your

[Issue 18021] FileLogger Member not accessible to subclasses

https://issues.dlang.org/show_bug.cgi?id=18021 --- Comment #1 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/21df9ea699cb54d19a96ad31c0b8143d4c58ac18 fix issue 18021

[Issue 18021] FileLogger Member not accessible to subclasses

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

Re: Thoughts about D

On 11/29/17 11:50 PM, Nicholas Wilson wrote: On Thursday, 30 November 2017 at 04:21:20 UTC, Steven Schveighoffer wrote: On 11/29/17 10:29 PM, Walter Bright wrote: Another issue (I should check this again) was doing null checks on member function calls, which is not necessary since if they're

Re: Attributes on Enum Members: Call for use cases.

On 11/30/17 3:34 AM, Timon Gehr wrote: On 29.11.2017 20:49, Steven Schveighoffer wrote: I would say: struct attribute1{} struct attribute2{} int foo(@attribute1 int x){ return x; } int bar(@attribute2 int y){ return y; } pragma(msg, typeof()); // int function(@attribute1 int x)? int

Re: Attributes on Enum Members: Call for use cases.

On 11/30/17 3:26 AM, Timon Gehr wrote: On 30.11.2017 00:23, Steven Schveighoffer wrote: Looking at std.traits, it looks like we use this mechanism to get everything: int func(int param1) static if(is(typeof(func) F == __parameters)) { static assert(is(typeof(F[0]) == int)); static

Re: First Impressions!

On Tuesday, 28 November 2017 at 16:14:52 UTC, Jack Stouffer wrote: you can apply attributes to your whole project by adding them to main void main(string[] args) @safe {} Although this isn't recommended, as almost no program can be completely safe. In fact I believe it is. When you have

Re: Beta 2.077.1

On 11/26/2017 02:27 PM, Paolo Invernizzi wrote: > 18012 is an ice regression towards 2.076.1 ... Fixed with 2.077.1, was a duplicate of https://issues.dlang.org/show_bug.cgi?id=17955.

Re: Release D v2.077.1

On 30/11/2017 1:52 PM, Martin Nowak wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Glad to announce D v2.077.1. http://dlang.org/download.html This point release fixes a few issues over v2.077.1, see the changelog for more details. http://dlang.org/changelog/v2.077.1.html

Release D v2.077.1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Glad to announce D v2.077.1. http://dlang.org/download.html This point release fixes a few issues over v2.077.1, see the changelog for more details. http://dlang.org/changelog/v2.077.1.html - -Martin -BEGIN PGP SIGNATURE-

Re: Release D v2.076.1

On 10/13/2017 04:50 AM, Jonathan M Davis wrote: >> With reg fixes put in master at the same time that in stable, >> testing 3 versions of the DMD compiler would not be necessary >> anymore, i think. > > I don't know what the best way to handle committing regression fixes is Regression fixes (and

Re: Beta 2.077.1

On 11/26/2017 12:30 PM, Walter Bright wrote: > Too late for RAII for betterC? :-( Also see https://forum.dlang.org/post/oknjtm$1unb$1...@digitalmars.com for the release schedule. Next major release will be 2.078.0 on Jan 1 2018. Just make sure to finish and properly test any features in time.

Re: First Impressions!

On Thursday, 30 November 2017 at 11:41:09 UTC, Walter Bright wrote: On 11/30/2017 2:47 AM, Nicholas Wilson wrote: As far as I can tell, pretty much the only users of UTF16 are Windows programs. Everyone else uses UTF8 or UCS32. I assume you meant UTF32 not UCS32, given UCS2 is Microsoft's

Re: First Impressions!

On Thursday, 30 November 2017 at 10:19:18 UTC, Walter Bright wrote: On 11/27/2017 7:01 PM, A Guy With an Opinion wrote: +- Unicode support is good. Although I think D's string type should have probably been utf16 by default. Especially considering the utf module states: "UTF character

[Issue 18020] [Reg 2.078] no property opCmp for anon class

https://issues.dlang.org/show_bug.cgi?id=18020 --- Comment #2 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/dmd https://github.com/dlang/dmd/commit/da7e071e305989e85f9a7128ae0edda628e13148 Fix Issue 18020 - [Reg 2.078] no property opCmp for anon

Re: First Impressions!

On 11/30/2017 2:47 AM, Nicholas Wilson wrote: As far as I can tell, pretty much the only users of UTF16 are Windows programs. Everyone else uses UTF8 or UCS32. I assume you meant UTF32 not UCS32, given UCS2 is Microsoft's half-assed UTF16. I meant UCS-4, which is identical to UTF-32. It's

Re: First Impressions!

On 11/30/2017 2:39 AM, Joakim wrote: Java, .NET, Qt, Javascript, and a handful of others use UTF-16 too, some starting off with the earlier UCS-2: https://en.m.wikipedia.org/wiki/UTF-16#Usage Not saying either is better, each has their flaws, just pointing out it's more than just Windows.

Re: Instructions to build DMD from source don't work (anymore) here

On Thursday, 30 November 2017 at 10:47:57 UTC, Jacob Carlborg wrote: On 2017-11-30 09:56, Basile B. wrote: On Thursday, 30 November 2017 at 08:38:15 UTC, Basile B. wrote: [...] All required tools are setup. I do not set AUTOBOOTSTRAP=1 since dmd 2.077 is setup. I needed gcc-c++... I don't

Re: Thoughts about D

On 2017-11-30 04:23, Walter Bright wrote: At this point, relying on druntime not changing is just not realistic. libc is different, having been cast in stone for nearly 30 years now. There are still problems with libc on Linux. One cannot assume a binary compiled one distribution works on

Re: Chocolatey Packages for DMD, LDC, and GDC

On 2017-11-29 22:16, Manuel Maier wrote: That's the one nice thing about the dmd installer, it takes care of setting up the default environment for you if it detects Visual Studio to be installed. At one point DVM did modify the sc.ini/dmd.conf but for different reasons. But it turned out

Re: Thoughts about D

On Thursday, 30 November 2017 at 10:39:07 UTC, Ola Fosheim Grøstad wrote: On Thursday, 30 November 2017 at 09:01:20 UTC, Jonathan M Davis wrote: It's close enough. Instead of segfaulting when the member function is called, it'll segfault when it tries to access one of the member variables or

Re: Chocolatey Packages for DMD, LDC, and GDC

On 2017-11-29 21:44, Manuel Maier wrote: Thanks for pointing this out! Maybe it would be worthwhile to add some kind of "FAQ" or "Troubleshooting" section to the GitHub README of dvm. Done: https://github.com/jacob-carlborg/dvm#limitations -- /Jacob Carlborg

Re: Private imports and Objects

On Thursday, 30 November 2017 at 06:44:43 UTC, Jonathan M Davis wrote: On Thursday, November 30, 2017 06:29:43 helxi via Digitalmars-d-learn wrote: [] I don't understand the question. You're asking whether casting from a base class to a derived class creates overhead? Or are you asking

Re: Instructions to build DMD from source don't work (anymore) here

On 2017-11-30 09:56, Basile B. wrote: On Thursday, 30 November 2017 at 08:38:15 UTC, Basile B. wrote: [...] All required tools are setup. I do not set AUTOBOOTSTRAP=1 since dmd 2.077 is setup. I needed gcc-c++... I don't know why but since "which g++" gave a valid file name i thought it was

Re: First Impressions!

On Thursday, 30 November 2017 at 10:19:18 UTC, Walter Bright wrote: On 11/27/2017 7:01 PM, A Guy With an Opinion wrote: [...] Sooner or later your code will exhibit bugs if it assumes that char==codepoint with UTF16, because of surrogate pairs.

  1   2   >