<whitequark[cis]>
I think both are fairly complete
frgo has joined #amaranth-lang
frgo_ has quit [Read error: Connection reset by peer]
frgo_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
<cr1901>
computer trouble... both RFCs are merge for me as long as number.Real includes ints (and I hope it would :P), won't be physically present at the meeting
<whitequark[cis]>
mine is merge, as I think all of the outstanding questions were resolved
<Chips4MakersakaS>
merge
<tpw_rules>
seems quite nice, thanks for the effort. merge!
<Wanda[cis]>
yeah let's merge this
<tpw_rules>
actually one minor q: what is Period(1)?
<tpw_rules>
assuming an error from "accepting at most one named argument"
<whitequark[cis]>
error
<whitequark[cis]>
(it doesn't accept unnamed arguments; although I imagine eventually it might accept a single one from unambiguous conversions from timedelta or another Period)
<whitequark[cis]>
* (it doesn't accept unnamed arguments; although I imagine eventually it might accept a single one for unambiguous conversions from timedelta or another Period)
<Wanda[cis]>
Period(0) would also be unambigous (but I don't think it'd be very useful)
<whitequark[cis]>
I think we shouldn't accept that
<tpw_rules>
i agree on not acceptinbg
<whitequark[cis]>
okay, the disposition for RFC 71 is merge. that's it for today! thanks everyone
<_whitenotifier-3>
[amaranth-lang/amaranth-lang.github.io] whitequark a77cb80 - Deploying to main from @ amaranth-lang/rfcs@be658d7c84d5ed4081df40af5744185c6cb21d71 🚀
<tpw_rules>
is there like, a signup process for pypi? could/should i put a module up there that i expect like 3 people in my lab to use?