On 12/30/2017 11:23 PM, IM wrote:
While we are discussing it here, could you please let me know what the bug
triage process for each release cycle is? Is it random that anyone picks up
whatever bug s/he feels like fixing? Or is it that if contributors will
contribute X number of patches this cy
On Sunday, 31 December 2017 at 05:43:57 UTC, Walter Bright wrote:
On 12/30/2017 6:42 AM, Muld wrote:
In contrast this same problem exists for Bugzilla. You say
it's working cause it's better than using notepad or some
other stupid shit. Bugzilla isn't the issue, it's the fact the
people mainta
On 12/30/2017 6:42 AM, Muld wrote:
In contrast this same problem exists for Bugzilla. You say it's working cause
it's better than using notepad or some other stupid shit. Bugzilla isn't the
issue, it's the fact the people maintaining it aren't willing to commit to
anything and leave issues open
Am Sun, 17 Dec 2017 10:21:33 -0700
schrieb David Gileadi :
> On 12/17/17 3:28 AM, WebFreak001 wrote:
> > On Sunday, 17 December 2017 at 04:34:22 UTC, David Gileadi wrote:
> > uh I don't know about stdx.data.json but if you didn't manage to succeed
> > yet, I know that asdf[1] works really well wi
On Sunday, 31 December 2017 at 02:06:03 UTC, Iain Buclaw wrote:
2. Feel free to look at the list of regressons.
https://issues.dlang.org/buglist.cgi?bug_severity=regression&component=dmd&list_id=218477&query_format=advanced&resolution=---
"This list is too long for Bugzilla's little min
On 31 December 2017 at 02:07, codephantom via Digitalmars-d
wrote:
> On Saturday, 30 December 2017 at 16:36:57 UTC, Iain Buclaw wrote:
>>
>>
>> All open issues are actionable, and require some action. They are not
>> noise, and many issues whose fix requires a change in language specification
>>
On 12/30/2017 04:07 AM, IM wrote:
I like what the D foundation did to the website, the language and
library docs, the Learn section, the forums, the resources ... etc. That
definitely gives the impression of maturity.
As far as I'm aware, the foundation isn't too active in those areas;
unless
On Saturday, 30 December 2017 at 21:40:29 UTC, Adam Wilson wrote:
This is not true. I was at DConf one year (can't remember
which) and I watched the representative of one of D's larger
corporate users do everything but actually get on his knees and
beg Walter to make a breaking change. IIRC t
On Saturday, 30 December 2017 at 16:36:57 UTC, Iain Buclaw wrote:
All open issues are actionable, and require some action. They
are not noise, and many issues whose fix requires a change in
language specification or semantics are understandably left to
the few who have the authoritative to m
On 12/30/2017 3:47 PM, rjframe wrote:
He does have a point. At work, people often email me directly, or stop me
in the hallway, to report things that belong on the issue tracker. I
consistently tell people that if I don't fix something the same day, it
likely isn't going to happen unless it's on
On 12/30/2017 3:04 PM, Nicholas Wilson wrote:
I can hear him already, "Post it on buzzkill or it won't get fixed!"
It's already on bugzilla, and was already fixed.
On Sat, 30 Dec 2017 23:04:21 +, Nicholas Wilson wrote:
> I can hear him already, "Post it on buzzkill or it won't get fixed!"
He does have a point. At work, people often email me directly, or stop me
in the hallway, to report things that belong on the issue tracker. I
consistently tell peop
On Saturday, 30 December 2017 at 23:04:21 UTC, Nicholas Wilson
wrote:
I can hear him already, "Post it on buzzkill or it won't get
fixed!"
Stupid autocorrect. Bugzilla.
On Thursday, 28 December 2017 at 03:31:19 UTC, ChangLong wrote:
Hi Walter, Can you take a look at this betterC bug:
https://issues.dlang.org/show_bug.cgi?id=18099
==
struct D()
{
struct V {
~this() {
}
On 12/27/17 00:10, Pawn wrote:
On Wednesday, 27 December 2017 at 09:39:22 UTC, codephantom wrote:
IMHO..What will help the cause, in terms of keeping D as a 'modern'
programming language, is the willingness of its designers and its
community to make and embrace 'breaking changes' ... for example
On Saturday, 23 December 2017 at 09:10:25 UTC, Walter Bright
wrote:
On 12/22/2017 7:23 AM, Russel Winder wrote:
I think we are now in a world where Rust is the zero cost
abstraction
language to replace C and C++, except for those who are
determined to
stay with C++ and evolve it.
Maybe it is
On Thursday, 28 December 2017 at 11:56:24 UTC, Russel Winder
wrote:
And is the way every programmer learns their non-first
language. All newly learned programming languages are merged
into a person's "head language" which is based on their first
language but then evolves as new languages, espec
On Sunday, 24 December 2017 at 16:51:45 UTC, Patrick Schluter
wrote:
That's the biggest problem with C++, they pile on relentlessly
half baked feature after half baked feature in a big dump that
no one with a life can ever grasp.
I think D has more first class language features (and thus
spec
In this video[1] from 2016, developer talks about C++ memory
safety features, meta-programming, maturity and few others as
main reasons they choose it for developing their blockchain
software (the way I got it from a quick view).
Besides, D maturity (which I can't confirm or deny), what else
On Thursday, 28 December 2017 at 16:43:41 UTC, John Gabriele
wrote:
On Thursday, 28 December 2017 at 15:57:18 UTC, Paulo Pinto
wrote:
On Thursday, 28 December 2017 at 11:27:29 UTC, Russel Winder
wrote:
On Wed, 2017-12-27 at 18:41 +, Laeeth Isharc via
Digitalmars-d wrote:
[…]
However the
On 30 December 2017 at 15:42, Muld via Digitalmars-d
wrote:
> On Saturday, 30 December 2017 at 06:55:13 UTC, Walter Bright wrote:
>>
>> It's not like we have a shortage of bugzilla issues and are wondering what
>> to do next.
>
>
> Yah there are a ton of Bugzilla issues, that's the problem. More t
On Saturday, 30 December 2017 at 06:55:13 UTC, Walter Bright
wrote:
It's not like we have a shortage of bugzilla issues and are
wondering what to do next.
Yah there are a ton of Bugzilla issues, that's the problem. More
than half of them aren't "actionable" as you put it.
Here's the problem,
On Friday, 29 December 2017 at 23:27:38 UTC, Walter Bright wrote:
On 12/29/2017 3:15 PM, Muld wrote:
Bugzilla is a huge mess tbh, creating a request in bugzilla
won't lead anywhere.
Fixes for bugzilla issues are posted on github nearly every day.
This does not mean anything, just cause fixes
I try to find a way to yield custom fiber without throw
exception, is it possible ?
I need make sure the scope guard is executed and the resource
will auto release relay on scope(exit).
After fiber yield, the spoke guard is not able to execute,
unless I throw a exception in Fiber. I am lo
On 12/27/17 6:28 PM, Tofu Ninja wrote:
On Sunday, 24 December 2017 at 05:21:44 UTC, Tofu Ninja wrote:
I didn't get any response in learn for this so I will ask it here.
TypeInfo_Class.interfaces[n].classinfo has TypeInfo_Class and not
TypeInfo_Interface?
Is this correct? Or is it a bug?
Does
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
-- Better compiler errors, better compiler errors, better
compiler errors.
I really wish that the compiler errors could receive some
refinement. Mostly it feels like some error text just being
thrown at me. It needs to
On Friday, 29 December 2017 at 22:05:31 UTC, I Love Stuffing
wrote:
On Friday, 29 December 2017 at 09:46:05 UTC, JN wrote:
AFAIK Rust doesn't have templates, but generics. Generics
usually have much cleaner error messages because they are
mostly used for generic functions and classes, meanwhile
On Saturday, 30 December 2017 at 07:30:39 UTC, Elronnd wrote:
On Friday, 29 December 2017 at 22:05:31 UTC, I Love Stuffing
wrote:
Also, for a mature D, some damn collections. Queues, Stacks,
Deques, etc...
std.container.dlist
(https://dlang.org/phobos/std_container_dlist.html)?
The queue or
28 matches
Mail list logo
