• Jonathan (5/5) Mar 29 2015 Hey folks,
• John Colvin (5/10) Mar 29 2015 That's a nice idea, but for now I'd say look for bugs with few
• Martin Nowak (15/21) Mar 30 2015 Sounds like a nice idea, but I doubt that it will work out.
• Jonathan (6/19) Mar 30 2015 Actually, this is a good alternative: post here if anyone knows
• Martin Nowak (3/10) Mar 30 2015 OK, it requires a little X86 knowledge, but if you make a pull, we can

"Jonathan" <jadit2 gmail.com> writes:

Hey folks,

I'm been starting to work on Debian bugs and found that most of 
the issues are eventually ranked from easy to hard to fix. I 
wondering if we can do the same (if not already). I think it 
would encourage new folks to pick up tasks (like myself).

"John Colvin" <john.loughran.colvin gmail.com> writes:

On Sunday, 29 March 2015 at 20:20:52 UTC, Jonathan wrote:
 Hey folks,

 I'm been starting to work on Debian bugs and found that most of 
 the issues are eventually ranked from easy to hard to fix. I 
 wondering if we can do the same (if not already). I think it 
 would encourage new folks to pick up tasks (like myself).

That's a nice idea, but for now I'd say look for bugs with few 
comments. Lots of comments normally implies there is a difficult 
problem and a solution hasn't been found, despite experienced 
people trying.

Martin Nowak <code+news.digitalmars dawg.eu> writes:

On 03/29/2015 10:20 PM, Jonathan wrote:
 Hey folks,
 
 I'm been starting to work on Debian bugs and found that most of the
 issues are eventually ranked from easy to hard to fix. I wondering if we
 can do the same (if not already). I think it would encourage new folks
 to pick up tasks (like myself).

Sounds like a nice idea, but I doubt that it will work out.
There are already plenty of tools to prioritize bugs, but people often
don't even set importance or severity.

We could try something different, let the core contributors weekly
curate bugs.

I'll start with a bunch of core.atomic improvements.

https://issues.dlang.org/show_bug.cgi?id=12891 - add atomicInc and
atomicDec to core.atomic
https://issues.dlang.org/show_bug.cgi?id=14117 - core.atomic should be  safe

That one is a bit harder, because it involves dmd and druntime, but it's
a huge improvement, implementation help guaranteed.

https://issues.dlang.org/show_bug.cgi?id=13713 - core.atomic should use
compiler intrinsics

-Martin

"Jonathan" <jadit2 gmail.com> writes:

Actually, this is a good alternative: post here if anyone knows 
about simple bugs that I can tackle.

Although Martin, I wouldn't considering writing patches involving 
atomic ops to be easy/simple bugs. However, I think I know enough 
x86 asm to write an optimized version of atomicInc and atomicDec. 
I'll take a crack at it this week!

 I'll start with a bunch of core.atomic improvements.

 https://issues.dlang.org/show_bug.cgi?id=12891 - add atomicInc 
 and
 atomicDec to core.atomic
 https://issues.dlang.org/show_bug.cgi?id=14117 - core.atomic 
 should be  safe

 That one is a bit harder, because it involves dmd and druntime, 
 but it's
 a huge improvement, implementation help guaranteed.

 https://issues.dlang.org/show_bug.cgi?id=13713 - core.atomic 
 should use
 compiler intrinsics

 -Martin

Martin Nowak <code+news.digitalmars dawg.eu> writes:

On 03/30/2015 05:19 PM, Jonathan wrote:
 Actually, this is a good alternative: post here if anyone knows about
 simple bugs that I can tackle.
 
 Although Martin, I wouldn't considering writing patches involving atomic
 ops to be easy/simple bugs. However, I think I know enough x86 asm to
 write an optimized version of atomicInc and atomicDec. I'll take a crack
 at it this week!

OK, it requires a little X86 knowledge, but if you make a pull, we can
help you with the details.