<cr1901>
Gonna be honest- I've been preoccupied w/ other things this week and have like 2000 lines of scrollback; is the diagnostic for "you created a memory incorrectly", as I do in Sentinel, upstream yet?
<Wanda[cis]>
yeah we merged it
<cr1901>
Cool, thanks
<Wanda[cis]>
but it only triggers when you actually use the elaboratable twice
<Wanda[cis]>
because we don't really have means of detecting where exactly things were created a mutated, only that you mutated things after elaboration
<cr1901>
That's not a problem; my pytests will cause that to trigger because of how I use parametric fixtures
<cr1901>
But having to pass in a functools.partial to elaborate a new object for each run of a parametric test is... kinda shitty from a usability standpoint, so I added it in as a hack
<cr1901>
(Thinking out loud: Maybe I can workaround this by doing copy.copy or copy.deepcopy and get rid of the partial hack)
lf_ has joined #amaranth-lang
lf has quit [Ping timeout: 268 seconds]
Degi has quit [Ping timeout: 268 seconds]
Degi_ has joined #amaranth-lang
Degi_ is now known as Degi
<whitequark[cis]>
<cr1901> "But having to pass in a functool..." <- when MemoryData lands you can use that