00:04 <d1b2> <chuckmcm> I have, and the kbob one. It's good.

00:25 <d1b2> <vipqualitypost> a bit outdated but the vivonomicon blog has some really nice stuff too

00:26 <d1b2> <vipqualitypost> although i'm sure you've found them all through the docs like i did 🙂

06:33 <_whitenotifier-8> [amaranth] yurivict opened issue #856: Plans for the next release? - https://github.com/amaranth-lang/amaranth/issues/856

20:44 <_whitenotifier-8> [amaranth] whitequark commented on issue #856: Plans for the next release? - https://github.com/amaranth-lang/amaranth/issues/856#issuecomment-1656316554

20:44 <_whitenotifier-8> [amaranth] whitequark closed issue #856: Plans for the next release? - https://github.com/amaranth-lang/amaranth/issues/856

21:59 <Tubbles> Hey all, any info on when v0.4 might be expected to land?

21:59 <whitequark[cis]> when it's ready

21:59 <Tubbles> Ok,

22:00 <whitequark[cis]> the limiting factor is my health

22:02 <Tubbles> Any indication of the amount of features left, some percentage or so? I am wondering what stability one might expect from the latest dev snapshot (sorry, hit enter too soon on the prev message so it looks really snarky)

22:02 <Tubbles> Sorry to hear about your health

22:03 <whitequark[cis]> https://github.com/amaranth-lang/amaranth/milestone/4

22:03 <whitequark[cis]> some of these things were handled by a contributor (charlottia) who also has pretty serious health issues lately

22:30 <galibert[m]> A lot of needs:rfc in there

22:31 <zyp[m]> that's a natural consequence of requiring larger changes to go through the RFC process

22:32 <galibert[m]> Sure, but that means most are not a “simple matter of programming”

22:33 <zyp[m]> making the decisions is often a larger job than doing the implementation

22:38 <zyp[m]> also, when the reference implementation is developed in parallel with the RFC, it might be ready for merging by the time the RFC is accepted

22:39 <whitequark[cis]> some of the RFCs are fairly trivial also