7. day: 9 bugs were removed (issues 9588, 11432, 15924, 17628, 17753, 19229, 19435, 20350, 20416)

8. day: 6 bugs were removed (issues 11738, 13066, 18815, 20309, 20364, 20438)

Thank you once again for your work!

Maybe add a line for each bug with the title of the bug report, so people can see what got fixed?

On Monday, 9 December 2019 at 14:17:43 UTC, FeepingCreature wrote:
> Maybe add a line for each bug with the title of the bug report, so people can see what got fixed?

Most of them are of the sort "wontfix", "invalid", "allready fixed", "duplicate", "is enhancement and not a bug", "wrong tool" and so on.  I think it's not really interesting to see these "fixes". That's the reason why I write "removed" and not "fixed"...

Having said this, there have been a few real fixes:

Day 1:
Issue 19105 - Bogus recursive template expansion via getSymbolsByUDA
              (unfortunatley meanwhile reopened)
Issue 20054 - getSymbolsByUDA no longer works on modules
Issue 20354 - interface is not supported by CanCAS in core.internal.atomic

Day 4:
Issue 16223 - BigUint: undefined shift for small instantiation type

Day 6:
Issue 19733 - expi documentation links broken
Issue 20396 - format!"%a" leeds to wrong result for denormalized float

Day 7:
Issue 9588 - format prints context pointer for struct
Issue 20350 - JSONType deprecations should be undeprecated
Issue 20416 - [Regression 2.073.2] compiler complains about escaping reference
              in certain cases

Day 8:
Issue 20364 - [REG2.069] changing length for typeof(null)[] array seg faults in
              _d_arraysetlengthiT()
Issue 20438 - [Reg 2.086] GC: memory not reusable when calling GC.collect after GC.free

And just to make it clear: Not all of these fixes have been made by me (indeed I made only 3 of these real ones) - I count *all* changes, looking at this as some sort of a community afford.

On Monday, 9 December 2019 at 15:37:07 UTC, berni44 wrote:

> And just to make it clear: Not all of these fixes have been made by me (indeed I made only 3 of these real ones) - I count *all* changes, looking at this as some sort of a community afford.

"Issues" forum seems to be offline - last change 4 days ago while on bugzilla there are a lot of more recent changes (e.g. the ones you listed here)

On Monday, 9 December 2019 at 16:52:47 UTC, Dominikus Dittes Scherkl wrote:
> "Issues" forum seems to be offline - last change 4 days ago while on bugzilla there are a lot of more recent changes (e.g. the ones you listed here)

There's a breakdown somewhere between Bugzilla and the NNTP server where the forum interface pulls all the posts from. I contacted the relevant parties a day ago.

9.day: 6 bugs were removed (issues 6641, 8224, 8947, 10465, 14630, 20431)

Real fixes:
Issue 20431 - Allow a Mixin Type to resolve to an expression where it makes sense

On Tuesday, 10 December 2019 at 08:59:52 UTC, berni44 wrote:
> 9.day: 6 bugs were removed (issues 6641, 8224, 8947, 10465, 14630, 20431)
>
> Real fixes:
> Issue 20431 - Allow a Mixin Type to resolve to an expression where it makes sense

Your total count now stands at 42! :-) [1]

[1]
https://en.wikipedia.org/wiki/42_(number)#The_Hitchhiker's_Guide_to_the_Galaxy

Thank you!

On Tuesday, 10 December 2019 at 08:59:52 UTC, berni44 wrote:
> 9.day: 6 bugs were removed (issues 6641, 8224, 8947, 10465, 14630, 20431)
>
> Real fixes:
> Issue 20431 - Allow a Mixin Type to resolve to an expression where it makes sense

I just wanted to say that this is a great idea and I am looking forward to the next "doors".
Thank you very much!

10. day: 15 bugs were removed (issues 4586, 4589, 4606, 5488, 8867, 13560, 15048, 17187, 18248, 18411, 19302, 19493, 19533, 20331, 20411)

Real fixes:
Issue 18248 - radix overload of std.conv.parse fails to throw on non-empty range
              without number
Issue 20331 - checkaction=context segfaults when calling function literal