Sébastien Bourdeauducq

I guess this line needs to be modified: https://github.com/haslersn/any-nix-shell/blob/master/bin/any-nix-shell#L15

This indeed fixes it for fish: ``` --- a/bin/any-nix-shell +++ b/bin/any-nix-shell @@ -12,7 +12,7 @@ end # Overwrite the nix command function nix - if test \$argv[1] = shell +...

``.any-nix-wrapper`` would also need an update, otherwise it seems ``nix develop`` gets aliased to ``nix shell``.

> Can you use `nix shell` instead of `nix develop`? Unfortunately ``nix shell`` means using ``pkgs.buildEnv`` and not ``pkgs.mkShell``. This means you cannot set environment variables in the shell from...

Sounds good. IIRC the only state that needs to be in the write domain is one pointer value modulo the size of the register, so we can never get that...

For the ``clear`` signal on the read side, all this will cause is glitches on the ``writable`` signal that perhaps don't matter (I wonder if they could actually cause missing...

> The oMigen simulator had a strange interface where user processes would run after a clock edge, but before synchronous signals assume their new value. The reason for this is...

Was this changed already? This prints ``1 0``: ```python from nmigen import * from nmigen.back.pysim import * class Dummy(Elaboratable): def __init__(self): self.x = Signal() self.y = Signal() def elaborate(self, platform):...

Yes. It is a dummy signal to work around #262.

What about an option to run synchronous processes at twice the clock rate? For example, a synchronous process could yield a full cycle (default), or a high half-cycle, or a...