<whitequark>
just built a glasgow applet with 100% wasm tools for the first time
<gruetzkopf>
neat
<tnt>
Has anyone looked into a webassembly softcore ?
<tnt>
nevermind, just took a glance at the specs ...
<awygle>
excellent work as always whitequark!
<Lofty>
tnt: if people can parse x86 in hardware, they can manage wasm /s
<tnt>
Lofty: well I saw "stack based" so I figured, maybe it's "simple / small" ... but requiring float/int 32/64 is a bad start :p
<d1b2>
<TiltMeSenpai> not quite glasgow related but is there a reason why nmigen uses the older generator style async syntax instead of the newer async/await style syntax?
<Lofty>
TiltMeSenpai: nmigen's minimum Python version is 3.6
<d1b2>
<TiltMeSenpai> ok cool
<Lofty>
async/await is 3.7, right?
<d1b2>
<TiltMeSenpai> wait, I think 3.4 has yield from, 3.5 introduced async/await, and about 3.7-ish, async/await became preferred
<d1b2>
<TiltMeSenpai> I don't remember exactly the order
<d1b2>
<TiltMeSenpai> https://www.python.org/dev/peps/pep-0492/ yeah, if we target 3.5, we could migrate to the async/await syntax. I think it's a big migration though
<d1b2>
<TiltMeSenpai> 3.5+*
<electronic_eel>
IIRC minimum python for glasgow currently is 3.6. it was once raised to 3.7, but I think that was a misunderstanding about argparse features and was then lowered to 3.6 again
<tnt>
And it's 3.7 again now :p
<d1b2>
<TiltMeSenpai> there's nothing functionally wrong with await from syntax, although I personally find it harder to read. I'd be willing to help with the migration to async/await but because it's a fairly major change without any serious functional improvement, I don't want to force this change on anyone
<d1b2>
<TiltMeSenpai> but 3.6 has async/await, so we could use it if we wanted
<electronic_eel>
tnt: ok, then I misremembered. thanks for correcting me
<awygle>
glasgow is 3.7 and nmigen is 3.6 iirc. i just talked to wq about this the other day
<sorear>
wasm is really remarkably hostile to hardware implementation, more so than even java
FFY00 has quit [Read error: Connection reset by peer]