whitequark[cis] changed the topic of #amaranth-lang to: Amaranth hardware definition language · weekly meetings: Amaranth each Mon 1700 UTC, Amaranth SoC each Fri 1700 UTC · play https://amaranth-lang.org/play/ · code https://github.com/amaranth-lang · logs https://libera.catirclogs.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
meithecatte[m] has quit [Quit: Idle timeout reached: 172800s]
Degi has quit [Ping timeout: 248 seconds]
Degi has joined #amaranth-lang
_whitelogger has joined #amaranth-lang
_whitenotifier-4 has quit [Ping timeout: 276 seconds]
galibert[m] has joined #amaranth-lang
<galibert[m]> Thanks Glasgow
<zyp[m]> <whitequark[cis]> if you're working on something that involves a fast reaction time (e.g. a fast paced shooter game), it's actually better to assert the output the moment the input gets asserted, then ignore deassertions until it stops bouncing
<zyp[m]> my proposed code does that; it lets the first state change through immediately, and ignores further state changes until the bounce timer is done
<whitequark[cis]> ah, nice!
vup has quit [Server closed connection]
vup has joined #amaranth-lang
_whitelogger has joined #amaranth-lang
conventia[m] has quit [Quit: Idle timeout reached: 172800s]
Lord_Nightmare has quit [Killed (ozone (No Spam))]
Lord_Nightmare has joined #amaranth-lang