nmigen-issue-migration

**Comment by [whitequark](https://github.com/whitequark)** _Monday Oct 28, 2019 at 10:44 GMT_ ---- In terms of the UI, currently `add_process` requires submitting explicit wait commands (i.e. `Tick("domain")`, and `add_sync_process(domain=)` automatically substitutes `yield...

**Comment by [jordens](https://github.com/jordens)** _Monday Oct 28, 2019 at 10:44 GMT_ ---- And this extends to multiple clock domains accordingly (sync cycles executed in the pattern defined by their timing beat...

**Comment by [jordens](https://github.com/jordens)** _Monday Oct 28, 2019 at 10:45 GMT_ ---- I don't think `BeforeTick`/`AfterTick` is sufficient: there are good reasons to do multiple delta cycles between sync cycles.

**Comment by [whitequark](https://github.com/whitequark)** _Monday Oct 28, 2019 at 10:45 GMT_ ---- Can you provide some examples of those reasons?

**Comment by [jordens](https://github.com/jordens)** _Monday Oct 28, 2019 at 10:56 GMT_ ---- Otherwise `yield x.eq(1)` could only ever been a sync update. If your process wants to do the equivalent of...

**Comment by [jordens](https://github.com/jordens)** _Monday Oct 28, 2019 at 11:00 GMT_ ---- E.g. if you don't have any synchronous clock domain. In the simplest case if you want to test whether...

**Comment by [whitequark](https://github.com/whitequark)** _Monday Oct 28, 2019 at 11:04 GMT_ ---- > If your process wants to do the equivalent of comb logic, this is limiting. Comb processes are something...

**Comment by [whitequark](https://github.com/whitequark)** _Monday Oct 28, 2019 at 11:08 GMT_ ---- Perhaps a trio of `yield Tick(domain)` (where if the domain is omitted, it is taken from the process), waiting...

**Comment by [jordens](https://github.com/jordens)** _Monday Oct 28, 2019 at 11:16 GMT_ ---- Yes. `yield Tick(domain)` will imply a `yield Settle()` just before the respective domain update. And now we can debate...

**Comment by [jordens](https://github.com/jordens)** _Monday Oct 28, 2019 at 11:19 GMT_ ---- The `yield Wait(signals)` (or `Watch()` or `Trigger()`) seems a bit orthogonal since it passively waits for some signal-related event...