00:16 <_whitenotifier-a> [YoWASP/nextpnr] whitequark pushed 1 commit to develop [+0/-0/±1] https://git.io/J4aOJ

00:16 <_whitenotifier-a> [YoWASP/nextpnr] whitequark c4a9071 - Update dependencies.

16:13 <mwbrown> Is there any way to write a helper function inside an nmigen simulation process that also returns a value? I know you have to `yield from` anything that talks to the sim because it's expecting a list of commands, but it seems that you cannot also return a value from a function you are yielding from

16:13 <mwbrown> example, you have some function that returns an integer after doing some state transitions... I tried something like `x = (yield from helper_function())`, but x is always None

16:14 <mwbrown> I'm thinking the only solution here would be to wrap it in some sort of stateful class to avoid littering my sim with globals

16:17 <d1b2> <DX-MON> if remembering correctly, the last statement in a generator function may be a normal return - this might help with this case

16:18 <mwbrown> I did try using a return at the very end of the function, but that didn't seem to do what I wanted. But also, aren't coroutines slightly different from generators? Or am I misunderstanding them since nmigen is the only place I've ever dealt with coros

16:18 <DX-MON> generators are functions that use yield statements

16:18 <DX-MON> coroutines are await/async

16:19 <DX-MON> I can't think of any instance in nMigen that uses the latter, only Glasgow

16:19 <mwbrown> Hmmm. Maybe I misread something

16:19 <mwbrown> I think the issue might be because it's doing `yield from` which is connecting the results of the yield all the way up to the generator

16:19 <mwbrown> er, not generator. Simulator

16:20 <DX-MON> so, if you want to get specific results out from the inner generator, you will most probably want to run a for loop (`for item in helper_function()`)

16:20 <DX-MON> inside that for loop, you then yield things you want going to the simulator

16:21 <mwbrown> That's what I was starting to think, yeah. Kind of hacky but I suppose I could write a class and do a type-check to see if it's a value my process cares about vs. something destined for the simulator

16:21 <DX-MON> and anything you don't want going to the sim, can then be handled in the loop

16:22 <mwbrown> Yep. I think I'm on the same page here. The real challenge would be trying to make that look clean, heh

16:23 <mwbrown> but then again, the code is already littered with yield from, so it's not gonna look that ugly by comparison

16:35 <vup> mwbrown: you can return from a helper function just fine: https://paste.niemo.de/ebinewodin.py

16:36 <vup> or are

16:36 <vup> you talking about returning multiple values?

16:44 <mwbrown> No, not multiple values. I just need to be able to return a single value at the end of a function. When I was trying it, it was giving me None as a return value... maybe my syntax was off. I'll give your example a try

16:44 <vup> fwiw my example works atleast for me :)

16:51 <mwbrown> Yep, works on my side too. I'll need to give what I did a second look and figure out why it was returning None

16:51 <mwbrown> this project I'm doing is my first real attempt with nMigen so I'm sure there's something I'm doing that's slightly off

18:29 <mwbrown> vup: it was indeed a stupid mistake. During my refactoring I moved the code in question to a new function, so the _inner_ function returns the value, but the outer function discards it and ultimately returns None :|

18:51 <vup> mwbrown: whoops, glad you could work it out