On Sunday, 31 December 2017 at 20:53:37 UTC, Muld wrote:
...
Stop making noise except one-day you make another well-known
language popular in the world called E.
What a kind of people who you are ? and can make such a noise to
well known and famous person who made such a great language?
On Friday, 5 January 2018 at 01:29:04 UTC, Laeeth Isharc wrote:
So it's highly unusual sets of people like that, or like the
founders of Sociomantic, or like the EMSI guys, or Liran's guys
at Weka that are likely to be D adopters in the next wave. Not
people who can't see through error
On Saturday, 30 December 2017 at 03:07:57 UTC, IM wrote:
On Friday, 29 December 2017 at 17:29:47 UTC, Adam D. Ruppe
wrote:
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
This is the only thing I greatly
On Sunday, 31 December 2017 at 21:16:35 UTC, Walter Bright wrote:
On 12/31/2017 8:18 AM, IM wrote:
What do you think? Do you agree that a process is needed?
We've tried adding process before. It does not work, for the
simple reason that it requires a dedicated group of people to
dedicate
On Sunday, 31 December 2017 at 21:16:35 UTC, Walter Bright wrote:
On 12/31/2017 8:18 AM, IM wrote:
What do you think? Do you agree that a process is needed?
We've tried adding process before. It does not work, for the
simple reason that it requires a dedicated group of people to
dedicate
On 12/31/2017 12:53 PM, Muld wrote:
Fix your shit
A word to the wise. Being rude will just get you ignored by most everyone on
this n.g. We insist on professional demeanor and courtesy at all times.
Egregious behavior will get posts unceremoniously removed.
On 12/31/2017 8:18 AM, IM wrote:
What do you think? Do you agree that a process is needed?
We've tried adding process before. It does not work, for the simple reason that
it requires a dedicated group of people to dedicate time to it. Are you willing
to do that?
We have added process when
On Saturday, 30 December 2017 at 16:36:57 UTC, Iain Buclaw wrote:
Hey, I take offence to that.
https://issues.dlang.org/show_bug.cgi?id=17839
https://github.com/dlang/dmd/pull/7503
https://github.com/dlang/dmd/pull/7508
https://github.com/dlang/dmd/pull/7509
On Sunday, 31 December 2017 at 05:43:57 UTC, Walter Bright wrote:
Please join and help out.
I already have, and like I said there are problems with with the
current system. I don't feel like helping anymore cause anything
time I do my work just get dumped, and I've simply wasted my time.
On Sunday, 31 December 2017 at 11:27:41 UTC, Seb wrote:
Yes, Dlang-bot was able to detect stalled issues for a while,
but we didn't turn this on for all repositories. I have just
enabled it:
https://github.com/dlang-bots/dlang-bot/pull/153
For the moment, it is just labelling issues with
On Sunday, 31 December 2017 at 07:43:35 UTC, Walter Bright wrote:
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
On Sunday, 31 December 2017 at 09:37:35 UTC, Meta wrote:
On Saturday, 30 December 2017 at 14:42:45 UTC, Muld 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
On Saturday, 30 December 2017 at 14:42:45 UTC, Muld 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 than half of
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
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
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
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=dmd_id=218477_format=advanced=---
"This list is too long for Bugzilla's little mind"
Mmm..just imagine how our
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
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;
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
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
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
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
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
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,
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
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)?
On 12/29/2017 7:07 PM, IM wrote:
They start writing
some code, and eventually they hit one of those unhelpful compile error
messages, which could indicate one of the following:
- An error in the engineer's knowledge of the language which the compiler didn't
help to understand what it is so
Creating a bugzilla account takes a couple minutes. It is enough friction to
serve as a reasonable filter against spammers and junk postings.
It's not like we have a shortage of bugzilla issues and are wondering what to do
next.
It's working well enough for those who care enough to make an
On 12/29/2017 5:40 PM, Adam D. Ruppe wrote:
> [...]
PRs to fix bugzilla issues get submitted every day. I don't see a better way. I
can't monitor every forum, I rely on you and others to do so and submit the issues.
On Friday, 29 December 2017 at 17:29:47 UTC, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
This is the only thing I greatly care about anymore. Biggest
problem D has in real world
On Saturday, 30 December 2017 at 02:37:24 UTC, IM wrote:
Just curious, why Bugzilla and not something else?
Bugzilla was the most well-known solution at the time. Keep in
mind the D bugzilla has been around since 2006. As far as I
understand it, migration at this point is deemed a big pain.
On Saturday, 30 December 2017 at 01:40:39 UTC, Adam D. Ruppe
wrote:
On Friday, 29 December 2017 at 23:24:45 UTC, Walter Bright
wrote:
That's been closed for a while now.
Well, take your pick:
https://issues.dlang.org/show_bug.cgi?id=12694
https://issues.dlang.org/show_bug.cgi?id=13340
On Friday, 29 December 2017 at 23:24:45 UTC, Walter Bright wrote:
That's been closed for a while now.
Well, take your pick:
https://issues.dlang.org/show_bug.cgi?id=12694
https://issues.dlang.org/show_bug.cgi?id=13340
https://issues.dlang.org/show_bug.cgi?id=16059
You always tell people to
On Friday, 29 December 2017 at 23:32:45 UTC, Walter Bright wrote:
...
3. Ideally there'd be a url one could click on, not an error
code.
No URLs! (unless they point to 'local' documentation).
I do not want to become even more dependent on having access to
the internet, in order to
On 12/29/2017 1:57 PM, rjframe wrote:
I noticed the Rust error has a code, too (E0308); if better error messages
are too difficult to implement, assigning codes to error types and
documenting them on the wiki could be helpful. Once you've dealt with an
error type, the messages aren't that bad,
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.
It's so bad honestly it'd probably be less work just to create a new bugzilla
and port any relevant entries
On 12/29/2017 2:31 PM, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 21:30:35 UTC, Walter Bright wrote:
This is not actionable. What is actionable is filing bugzilla enhancement
requests with specific examples.
I've done better than that: I've written pull requests.
On Friday, 29 December 2017 at 21:30:35 UTC, Walter Bright wrote:
On 12/29/2017 9:29 AM, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
This is the only thing I greatly care about
On Friday, 29 December 2017 at 21:30:35 UTC, Walter Bright wrote:
This is not actionable. What is actionable is filing bugzilla
enhancement requests with specific examples.
I've done better than that: I've written pull requests.
https://github.com/dlang/dmd/pull/6806
There's also existing
On Friday, 29 December 2017 at 21:56:26 UTC, Seb wrote:
On Friday, 29 December 2017 at 21:34:14 UTC, Walter Bright
wrote:
On 12/28/2017 11:53 PM, IM wrote:
Simple things like these make a big difference. D Lang has
been around for a long while now, and hence signs of its
maturity has to show
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
templates can do that too but much, much more, but when they
On Fri, 29 Dec 2017 13:34:14 -0800, Walter Bright wrote:
> On 12/28/2017 11:53 PM, IM wrote:
>> Simple things like these make a big difference. D Lang has been around
>> for a long while now, and hence signs of its maturity has to show
>> everywhere, especially in the compiler, as well as the
On Friday, 29 December 2017 at 21:34:14 UTC, Walter Bright wrote:
On 12/28/2017 11:53 PM, IM wrote:
Simple things like these make a big difference. D Lang has
been around for a long while now, and hence signs of its
maturity has to show everywhere, especially in the compiler,
as well as the
On 12/28/2017 11:53 PM, IM wrote:
Simple things like these make a big difference. D Lang has been around for a
long while now, and hence signs of its maturity has to show everywhere,
especially in the compiler, as well as the package manager.
Diverging from the:
file(line): message
format
On 12/29/2017 9:29 AM, Adam D. Ruppe wrote:
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better compiler errors.
This is the only thing I greatly care about anymore. Biggest problem D has in
real world use.
This is not
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
Very much so.
I actually made a list a day or two ago. Some of it is more
speculative than concrete, though:
* unicode categories to determine what can be an
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
-- Better compiler errors, better compiler errors, better
compiler errors.
This is the only thing I greatly care about anymore. Biggest
problem D has in real world use.
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
cut...
Simple things like these make a big difference. D Lang has been
around for a long while now, and hence signs of its maturity
has to show everywhere, especially in the compiler, as well as
the package manager.
I
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
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
[...]
Simple things like these make a big difference. D Lang has been
around for a long while now, and hence signs of its maturity
has to show everywhere, especially in the compiler, as well as
the package manager.
I
On 29/12/2017 11:03 AM, maarten van damme wrote:
>I'd like to see proper DLL (shared library) support and DIP45
implemented. I'm making a project that I hope in the future will be
extendable with D plugins.
Out of curiousity, what's wrong with the current dll support?
The starting problem
>I'd like to see proper DLL (shared library) support and DIP45 implemented.
I'm making a project that I hope in the future will be extendable with D
plugins.
Out of curiousity, what's wrong with the current dll support?
2017-12-29 11:36 GMT+01:00 angel via Digitalmars-d <
Built-in tuples:
{val1, val2} = func();
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
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
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 templates can do that
too but much, much more, but when they break, you get entire
paragraphs of template errors.
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
On Friday, 29 December 2017 at 07:53:51 UTC, IM wrote:
I will start:
I will add:
// --
module test;
import std.stdio;
@safe void main()
{
writeln("I'd like to see @safe as being the default");
}
//
You should fill an issue on issues.dlang.org for this particular case.
Compile should give you some hint, that you should use lvalue instead of
rvalue.
On Fri, Dec 29, 2017 at 8:53 AM, IM via Digitalmars-d <
digitalmars-d@puremagic.com> wrote:
> I will start:
>
>-- Better compiler errors,
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 be better formatted, more helpful, with
suggestions
60 matches
Mail list logo