On Tuesday, 19 December 2017 at 09:54:05 UTC, Walter Bright wrote:
"C, Python, Go, and the Generalized Greenspun Law"
http://esr.ibiblio.org/?p=7804
So .. and this is more of a question, to the maintainers and
creators of D, what does this mean for D, what is the road map
for D
- More supp
On Saturday, 30 December 2017 at 13:48:16 UTC, ChangLong wrote:
After fiber yield, the spoke guard is not able to execute,
unless I throw a exception in Fiber. I am look if there is
some hack method to make the fiber Interrupted at any time with
scope(exit) code executed.
There isn't. In f
On Sun, 31 Dec 2017 17:19:22 -0700, Jonathan M Davis wrote:
> Yes, it would be a pain to switch away from github at this point, but if
> github went down permanently tomorrow, it would just be an annoying
> roadblock. We almost certainly wouldn't lose any code (at most, a few
> commits, if no one
On Sun, 31 Dec 2017 23:50:04 +, Mengu wrote:
> - d leadership is dusty and so are their tools. we are no js community
> and hope we never become anything like them but bugzilla is a hundred
> years old. i am on github, i am on this ml and i also need a bugzilla
> account?
That's probably not
On Saturday, 30 December 2017 at 13:48:16 UTC, ChangLong wrote:
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
On Sunday, December 31, 2017 11:18:26 Seb via Digitalmars-d wrote:
> On Saturday, 30 December 2017 at 02:50:48 UTC, Adam D. Ruppe
>
> wrote:
> > 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
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 tim
On Sunday, 31 December 2017 at 19:49:07 UTC, Meta wrote:
On Sunday, 31 December 2017 at 11:18:26 UTC, Seb wrote:
On Saturday, 30 December 2017 at 02:50:48 UTC, Adam D. Ruppe
wrote:
Bugzilla was the most well-known solution at the time. Keep
in mind the D bugzilla has been around since 2006. As
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 s
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
https://github.com/dlang/dmd/pul
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.
Bu
On Sunday, 31 December 2017 at 11:18:26 UTC, Seb wrote:
On Saturday, 30 December 2017 at 02:50:48 UTC, Adam D. Ruppe
wrote:
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
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 e.g.
On Sunday, 31 December 2017 at 14:51:24 UTC, Russel Winder wrote:
The results are based on experimental data. Read the papers
rather than my waffle about them.
I'd love to, but I haven't found the specific paper. She seems to
work on many different things related to software design and
visual
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 Sat, 2017-12-30 at 17:53 +, Ola Fosheim Grøstad via Digitalmars-
d wrote:
> 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
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 of
On Saturday, 30 December 2017 at 02:50:48 UTC, Adam D. Ruppe
wrote:
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
On Saturday, 30 December 2017 at 16:59:41 UTC, aberba wrote:
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).
Be
On Saturday, 30 December 2017 at 16:59:41 UTC, aberba wrote:
Besides, D maturity (which I can't confirm or deny), what else
does D miss to be considered a better alternative for
blockchain in 2018?
You can write blockchain software in any language you want. The
reference implementation for Op
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 t
22 matches
Mail list logo
